biztrac. BETA
COMPANY REGISTER PROFILE
971422505 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of professional membership organisations

FORSKERFORBUNDET

Org. no. 971422505 Association/club/organisation (FLI) Oslo Incorporated 1976 Active
Ownership graph ↗
Revenue 2025 NOK 174.9m
Operating profit NOK −3.8m
Equity NOK 149.4m
Incorporated 1976
Employees 49

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3,8 mill kr).

FORSKERFORBUNDET is registered as a association/club/organisation in Oslo, Oslo with organisation number 971422505. The business is classified under activities of professional membership organisations (NACE 94.120). The company was incorporated in 1976 and has 49 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 174.9m in revenue and NOK −3.8m in operating profit.

Former names: NORSK FORSKERFORBUND

Key figures · 2025

Revenue
NOK 174.9m
▲ +3 %
Operating profit
NOK −3.8m
▲ +83 %
Equity
NOK 149.4m
▲ +15 %
Est. value
NOK 204.9m

Financial health · 2025

Liquidity
4.62
Very good
Current assets ÷ current liabilities
Profitability
10.7%
Good
Return on total assets
Solidity
71.5%
Very good
Equity as a share of total capital

Who owns FORSKERFORBUNDET?

No shareholders are registered for FORSKERFORBUNDET in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does FORSKERFORBUNDET own?

FORSKERFORBUNDET holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FORSKERFORBUNDET

What is the revenue of FORSKERFORBUNDET?

FORSKERFORBUNDET had revenue of NOK 174.9m in 2025.

Who is the general manager of FORSKERFORBUNDET?

Birgitte Olafsen is registered as general manager of FORSKERFORBUNDET.

Where is FORSKERFORBUNDET based?

FORSKERFORBUNDET has its business address in Oslo.

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

Report a problem

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