BIZTRAC BETA
General medical practice activities

FARHAN RAFIQUE AS

Org. no. 812119672 Limited company (AS) Fredrikstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 1.0m
Equity NOK 3.5m
Incorporated 2013
Share capital NOK 30,000

FARHAN RAFIQUE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 812119672. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av legepraksis, investering i andre selskap og verdipapirer og annet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 1.0m
Equity
NOK 3.5m
Est. value
NOK 5.9m

Financial health · 2024

Liquidity
2.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.8%
Very good
Equity as a share of total capital

Who owns FARHAN RAFIQUE AS?

FARHAN RAFIQUE
FARHAN RAFIQUE AS
NOK 4.1m rev. · NOK 1.0m profit

FARHAN RAFIQUE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FARHAN RAFIQUE AS own?

FARHAN RAFIQUE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FARHAN RAFIQUE AS

Who owns FARHAN RAFIQUE AS?

FARHAN RAFIQUE is the largest registered owner, with 100.0%.

What is the revenue of FARHAN RAFIQUE AS?

FARHAN RAFIQUE AS had revenue of NOK 4.1m in 2024.

Who is the general manager of FARHAN RAFIQUE AS?

Farhan Rafique is registered as general manager of FARHAN RAFIQUE AS.

Where is FARHAN RAFIQUE AS based?

FARHAN RAFIQUE AS has its business address in Fredrikstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.