FCC.reportPublic regulatory filings
FCC Registration Number

FRN 0027215615

Fengmi (Beijing) Technology Co., Ltd

CORES registration

Entity name
Fengmi (Beijing) Technology Co., Ltd
Entity type
Private Sector , Corporation
Registration date
2018-02-06
FCC source updated
2018-05-14
Contact position
DQA manager
Contact name
Dr GuoBo Hou
Contact address
301,3F,Building3,No.10,Shunyi District Renhe Town Barracks South Street, Beijing, China
CORES status
available
Last checked
2026-08-27 18:17:40

Connected companies

CompanyRelationshipSourceConfidence
Fengmi (Beijing) Technology Co., Ltd.registrantCORES100.0%
Fengmi (Beijing) Technology Co., Ltd.registrantFCCID100.0%
Fengmi (Beijing) Technology Co., Ltd.applicantFCCID95.0%

Public regulatory phone numbers

NumberContactSourceConfidence
+86 188 1868 9130Dr GuoBo Hou DQA managerCORES100.0%

FCC ID filings

DateFCC IDModelApplicant
2021-06-302AO2D-M055MGNM055MGNFengmi (Beijing) Technology Co., Ltd.
2021-06-302AO2D-M055MGNM055MGNFengmi (Beijing) Technology Co., Ltd.
2021-06-302AO2D-L176FGNL176FGNFengmi (Beijing) Technology Co., Ltd.
2021-06-302AO2D-L176FGNL176FGNFengmi (Beijing) Technology Co., Ltd.
2021-06-302AO2D-M055MGNM055MGNFengmi (Beijing) Technology Co., Ltd.
2021-06-302AO2D-L176FGNL176FGNFengmi (Beijing) Technology Co., Ltd.
2021-03-152AO2D-RC605RC605Fengmi (Beijing) Technology Co., Ltd.
2020-07-022AO2D-L176FGNL176FGNFengmi (Beijing) Technology Co., Ltd.
2020-07-022AO2D-L176FGNL176FGNFengmi (Beijing) Technology Co., Ltd.
2020-07-022AO2D-L176FGNL176FGNFengmi (Beijing) Technology Co., Ltd.
2020-03-052AO2D-RC603-MG2RC603-MG2Fengmi (Beijing) Technology Co., Ltd.
2020-01-182AO2D-M055FGNM055FGNFengmi (Beijing) Technology Co., Ltd.
2020-01-182AO2D-M055FGNM055FGNFengmi (Beijing) Technology Co., Ltd.
2020-01-182AO2D-M055FGNM055FGNFengmi (Beijing) Technology Co., Ltd.
2019-12-112AO2D-M055MGNM055MGNFengmi (Beijing) Technology Co., Ltd.
2019-12-112AO2D-M055MGNM055MGNFengmi (Beijing) Technology Co., Ltd.
2019-12-112AO2D-M055MGNM055MGNFengmi (Beijing) Technology Co., Ltd.
2018-07-162AO2D-MJJGYY02FMMJJGYY02FMFengmi (Beijing) Technology Co., Ltd.
2018-07-122AO2D-MJJGYY02FMMJJGYY02FMFengmi (Beijing) Technology Co., Ltd.
2018-07-122AO2D-MJJGYY02FMMJJGYY02FMFengmi (Beijing) Technology Co., Ltd.
2018-06-142AO2D-YKF429-004YKF429-004Fengmi (Beijing) Technology Co., Ltd.

Source provenance

SystemRecordRecorded nameRaw FRNObserved
FCCIDoAQX11MfCvoDsQHzbc7Rfw==:2AO2D-L176FGNFengmi (Beijing) Technology Co., Ltd.00272156152026-09-12 07:15:39
FCCIDnWojBsiC0zBdg7s8Cpyj4w==:2AO2D-MJJGYY02FMFengmi (Beijing) Technology Co., Ltd.00272156152026-09-11 11:45:30
FCCIDmLUkDM6Mqbl66cR1PQn7NQ==:2AO2D-M055MGNFengmi (Beijing) Technology Co., Ltd.00272156152026-09-09 19:45:27
FCCIDLOsIwZlqNTjZDk+yIBWK6Q==:2AO2D-M055FGNFengmi (Beijing) Technology Co., Ltd.00272156152026-09-08 09:45:19
FCCIDkIuNThowAdpVXTeD5r9AIw==:2AO2D-M055MGNFengmi (Beijing) Technology Co., Ltd.00272156152026-09-04 04:15:03
FCCIDio6v3SO11Pd5G92RngZJ0g==:2AO2D-MJJGYY02FMFengmi (Beijing) Technology Co., Ltd.00272156152026-08-28 10:44:35
CORES0027215615Fengmi (Beijing) Technology Co., Ltd00272156152026-08-27 18:17:40
FCCIDAyBsHzBzNJBkNqK8oUeZiA==:2AO2D-M055FGNFengmi (Beijing) Technology Co., Ltd.00272156152026-08-11 18:48:55
FCCIDAaMPM6XRXVnaT5Y1h2Z8CQ==:2AO2D-M055FGNFengmi (Beijing) Technology Co., Ltd.00272156152026-08-10 15:18:50
FCCID9wKl6oWxs748QIaaCcilTA==:2AO2D-YKF429-004Fengmi (Beijing) Technology Co., Ltd.00272156152026-08-10 04:18:47
FCCID7GmQvgPSzcKqRqFoNFKMuA==:2AO2D-M055MGNFengmi (Beijing) Technology Co., Ltd.00272156152026-08-07 20:18:39
FCCID63QF+TKKuWU/jhgMrJeQ3Q==:2AO2D-M055MGNFengmi (Beijing) Technology Co., Ltd.00272156152026-08-06 16:18:33
FCCID4OTjW23AAMAKx+yFVSAhXA==:2AO2D-RC605Fengmi (Beijing) Technology Co., Ltd.00272156152026-08-05 18:18:28
FCCID210742Fengmi (Beijing) Technology Co., Ltd.00272156152026-08-04 15:48:19
FCCID2jvNoLQu+LH2+6ufZrdctg==:2AO2D-M055MGNFengmi (Beijing) Technology Co., Ltd.00272156152026-08-04 10:48:23

Refresh this FRN

Request a background refresh from the FCC CORES public registration record. The page request does not contact the FCC directly.