BIZTRAC BETA
General medical practice activities

FRISK LEGEKONTOR AS

Org. no. 998752396 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 4.1m
Equity NOK 6.3m
Incorporated 2012
Share capital NOK 30,000

FRISK LEGEKONTOR AS is registered as a limited company in Oslo, Oslo with organisation number 998752396. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive legevirksomhet og hva hermed står i forbindelse, samt deltakelse i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 4.1m in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 4.1m
Equity
NOK 6.3m
Est. value
NOK 16.4m

Financial health · 2024

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

Who owns FRISK LEGEKONTOR AS?

FOLKE LOUIS BLIX
FRISK LEGEKONTOR AS
NOK 7.1m rev. · NOK 4.1m profit

FRISK LEGEKONTOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRISK LEGEKONTOR AS own?

FRISK LEGEKONTOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRISK LEGEKONTOR AS

Who owns FRISK LEGEKONTOR AS?

FOLKE LOUIS BLIX is the largest registered owner, with 100.0%.

What is the revenue of FRISK LEGEKONTOR AS?

FRISK LEGEKONTOR AS had revenue of NOK 7.1m in 2024.

Who is the general manager of FRISK LEGEKONTOR AS?

Folke Louis Blix is registered as general manager of FRISK LEGEKONTOR AS.

Where is FRISK LEGEKONTOR AS based?

FRISK LEGEKONTOR AS has its business address in Oslo.

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.