BIZTRAC BETA
Activities auxiliary to insurance and pension funding n.e.c.

LOFAVØR AS

Org. no. 964422206 Limited company (AS) Oslo Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 83.1m
Operating profit NOK −2.5m
Equity NOK 30.6m
Incorporated 1992
Employees 21
Share capital NOK 275,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,5 mill kr).

LOFAVØR AS is registered as a limited company in Oslo, Oslo with organisation number 964422206. The business is classified under activities auxiliary to insurance and pension funding n.e.c. (NACE 66.290). The company was incorporated in 1992 and has 21 registered employees. Registered share capital is NOK 275,000, divided into 5500 shares. The company's stated purpose is: “Drive forretningsvirksomhet, herunder å drive medlems- og fordelskonsepter for andre organisasjoner, og virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 83.1m in revenue and NOK −2.5m in operating profit.

Key figures · 2024

Revenue
NOK 83.1m
Operating profit
NOK −2.5m
Equity
NOK 30.6m
Est. value
NOK 55.2m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.1%
Good
Equity as a share of total capital

Who owns LOFAVØR AS?

LANDSORGANISASJONEN I NORGE
LOFAVØR AS
NOK 83.1m rev. · NOK −2.5m profit

LOFAVØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOFAVØR AS

Who owns LOFAVØR AS?

LANDSORGANISASJONEN I NORGE is the largest registered owner, with 51.0%.

What is the revenue of LOFAVØR AS?

LOFAVØR AS had revenue of NOK 83.1m in 2024.

Who is the general manager of LOFAVØR AS?

Heidi Lisbeth Myhr is registered as general manager of LOFAVØR AS.

Where is LOFAVØR AS based?

LOFAVØR 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.