Hashbyte Fintech Limited
赫希金融科技有限公司
About this company
Hashbyte Fintech Limited is a Hong Kong private company limited by shares incorporated on November 24, 2016. It is registered with company registration (CR) number 2455773 and business registration number (BRN) 66953699. It is one of 145,779 companies incorporated in Hong Kong in 2016. The company is currently active on the Hong Kong Companies Register and has been marked dormant since February 9, 2026. It previously operated under the name Hongkong De Feng Technology Development Limited until November 6, 2023. Its registered office is at 6/F ANCHANG FACTORY BLDG 19 TAI YIP ST KWUN TONG KLN HONG KONG. There are 24 documents on file with the Companies Registry dating back to 2016, most recently (C)Special Resolution (Dormant Company) filed on February 9, 2026.
Company Information
- CR Number
- 2455773
- BRN
- 66953699
- Company Type
- Private company limited by shares
- Type Category
- Local company
Dates & Status
- Incorporation Date
- 2016-11-24
- Has Charges
- No
- Dormant
- Yes
- Dormancy Start
- 2026-02-09
Compliance & Flags
- One-member Company
- Yes 2023-11-24
Registered office
Current address
6/F ANCHANG FACTORY BLDG 19 TAI YIP ST KWUN TONG KLN HONG KONG
Name History
| Name | From | To |
|---|---|---|
| 赫希金融科技有限公司 | 2023-11-06 | Current |
| 香港德豐科技發展有限公司 | 2016-11-24 | 2023-11-06 |
| Hashbyte Fintech Limited | 2023-11-06 | Current |
| Hongkong De Feng Technology Development Limited | 2016-11-24 | 2023-11-06 |
Company Documents
(C)Special Resolution (Dormant Company)
2026-02-09 · Other
(E)FNAR1 - Annual Return
2025-12-03 · Annual Return
(E)FNAR1 - Annual Return
2024-11-29 · Annual Return
(E)FNR2 - Notice of Location of Registers and Company Records
2024-11-29 · Other
(E)FND2A - Notice of Change of Company Secretary and Director (Appointment/Cessation)
2024-09-03 · Director/Secretary Change
Information Sheet regarding Using Business Registration Number as Unique Business Identifier
2023-12-24 · Other
(E)FNAR1 - Annual Return
2023-12-07 · Annual Return
(E)FNNC2 - Notice of Change of Company Name
2023-11-06 · Name Change
Certificate of Change of Name
2023-11-06 · Name Change
(E)FNAR1 - Annual Return
2022-11-24 · Annual Return
(E)FNAR1 - Annual Return
2021-12-01 · Annual Return
(E)FNAR1 - Annual Return
2020-11-24 · Annual Return
(E)FNAR1 - Annual Return
2019-11-25 · Annual Return
(E)FND2A - Notice of Change of Company Secretary and Director (Appointment/Cessation)
2019-11-25 · Director/Secretary Change
(E)FNR2 - Notice of Location of Registers and Company Records
2019-11-25 · Other
(E)FND4 - Notice of Resignation of Company Secretary and Director
2019-05-22 · Director/Secretary Change
(E)FNAR1 - Annual Return
2018-11-27 · Annual Return
(E)FND2A - Notice of Change of Company Secretary and Director (Appointment/Cessation)
2018-11-27 · Director/Secretary Change
(E)FND4 - Notice of Resignation of Company Secretary and Director
2018-09-13 · Director/Secretary Change
(E)FNR2 - Notice of Location of Registers and Company Records
2018-04-18 · Other
| Document | Type | Filing Date | Order |
|---|---|---|---|
| (C)Special Resolution (Dormant Company) | Other | 2026-02-09 | |
| (E)FNAR1 - Annual Return | Annual Return | 2025-12-03 | |
| (E)FNAR1 - Annual Return | Annual Return | 2024-11-29 | |
| (E)FNR2 - Notice of Location of Registers and Company Records | Other | 2024-11-29 | |
| (E)FND2A - Notice of Change of Company Secretary and Director (Appointment/Cessation) | Director/Secretary Change | 2024-09-03 | |
| Information Sheet regarding Using Business Registration Number as Unique Business Identifier | Other | 2023-12-24 | |
| (E)FNAR1 - Annual Return | Annual Return | 2023-12-07 | |
| (E)FNNC2 - Notice of Change of Company Name | Name Change | 2023-11-06 | |
| Certificate of Change of Name | Name Change | 2023-11-06 | |
| (E)FNAR1 - Annual Return | Annual Return | 2022-11-24 | |
| (E)FNAR1 - Annual Return | Annual Return | 2021-12-01 | |
| (E)FNAR1 - Annual Return | Annual Return | 2020-11-24 | |
| (E)FNAR1 - Annual Return | Annual Return | 2019-11-25 | |
| (E)FND2A - Notice of Change of Company Secretary and Director (Appointment/Cessation) | Director/Secretary Change | 2019-11-25 | |
| (E)FNR2 - Notice of Location of Registers and Company Records | Other | 2019-11-25 | |
| (E)FND4 - Notice of Resignation of Company Secretary and Director | Director/Secretary Change | 2019-05-22 | |
| (E)FNAR1 - Annual Return | Annual Return | 2018-11-27 | |
| (E)FND2A - Notice of Change of Company Secretary and Director (Appointment/Cessation) | Director/Secretary Change | 2018-11-27 | |
| (E)FND4 - Notice of Resignation of Company Secretary and Director | Director/Secretary Change | 2018-09-13 | |
| (E)FNR2 - Notice of Location of Registers and Company Records | Other | 2018-04-18 |
Delivered as a PDF to your email, normally within 24 hours. Full refund if we can't supply it.
Questions or bulk orders? orders@crhk.guru
crhk.guru is an independent service, not affiliated with the Hong Kong Companies Registry. Documents are plain copies of public records obtained from the Registry's e-Services on your behalf.
Related companies
Frequently asked questions
When was Hashbyte Fintech Limited incorporated?
Hashbyte Fintech Limited was incorporated in Hong Kong on November 24, 2016.
Is Hashbyte Fintech Limited still active?
Yes. Hashbyte Fintech Limited is currently active on the Hong Kong Companies Register. It is marked dormant (since February 9, 2026).
What are Hashbyte Fintech Limited's CR number and BRN?
Hashbyte Fintech Limited's company registration (CR) number is 2455773 and its business registration number (BRN) is 66953699.
Where is Hashbyte Fintech Limited's registered office?
Hashbyte Fintech Limited's registered office is at 6/F ANCHANG FACTORY BLDG 19 TAI YIP ST KWUN TONG KLN HONG KONG.
What type of company is Hashbyte Fintech Limited?
Hashbyte Fintech Limited is a private company limited by shares on the Hong Kong Companies Registry.
How many documents has Hashbyte Fintech Limited filed?
Hashbyte Fintech Limited has 24 documents on file with the Hong Kong Companies Registry, dating back to 2016.
Need this data via API? Full data and API access →