BIZTRAC BETA
Preventive health care activities

NORSK FAGFORUM AS

Org. no. 913462300 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 59,000
Operating profit NOK 32,000
Equity NOK 16,000
Incorporated 2014
Share capital NOK 30,000

NORSK FAGFORUM AS is registered as a limited company in Oslo, Oslo with organisation number 913462300. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Virksomheten skal omfatte, men ikke være begrenset til kursvirksomhet for helse og omsorgstjenester, utvikling og salg av software og hardware samt utleie av personell tilkyttet dette virksomhetsområdet.”. The most recent filed accounts, for the 2025 financial year, show NOK 59,000 in revenue and NOK 32,000 in operating profit.

Key figures · 2025

Revenue
NOK 59,000
Operating profit
NOK 32,000
Equity
NOK 16,000
Est. value
NOK 112,000

Financial health · 2025

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NORSK FAGFORUM AS?

ARNT JOHAN EGE
NORSK FAGFORUM AS
NOK 59,000 rev. · NOK 32,000 profit

NORSK FAGFORUM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORSK FAGFORUM AS

Who owns NORSK FAGFORUM AS?

ARNT JOHAN EGE is the largest registered owner, with 33.3%.

What is the revenue of NORSK FAGFORUM AS?

NORSK FAGFORUM AS had revenue of NOK 59,000 in 2025.

Who is the general manager of NORSK FAGFORUM AS?

Arnt Johan Ege is registered as general manager of NORSK FAGFORUM AS.

Where is NORSK FAGFORUM AS based?

NORSK FAGFORUM 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.