biztrac. BETA
COMPANY REGISTER PROFILE
998809681 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other education activities

OLAV ELVEMO AS

Org. no. 998809681 Limited company (AS) Bærum Incorporated 2012 Active
Revenue 2025 NOK 193,000
Operating profit NOK 154,000
Equity NOK −397,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−397k kr).

OLAV ELVEMO AS is registered as a limited company in Bærum, Akershus with organisation number 998809681. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kursvirksomhet og kognitiv terapi .”. The most recent filed accounts, for the 2025 financial year, show NOK 193,000 in revenue and NOK 154,000 in operating profit.

Key figures · 2025

Revenue
NOK 193,000
▼ −9 %
Operating profit
NOK 154,000
▲ +284 %
Equity
NOK −397,000
▲ +28 %
Est. value
NOK 560,000

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
81.7%
Very good
Return on total assets
Solidity
-172.9%
Weak
Equity as a share of total capital

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

Who owns OLAV ELVEMO AS?

OLAV ELVEMO AS
NOK 193,000 rev. · NOK 154,000 profit

OLAV ELVEMO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAV ELVEMO AS

Who owns OLAV ELVEMO AS?

Olav Elvemo is the largest registered owner, with 100.0%.

What is the revenue of OLAV ELVEMO AS?

OLAV ELVEMO AS had revenue of NOK 193,000 in 2025.

Who is the general manager of OLAV ELVEMO AS?

Olav Elvemo is registered as general manager of OLAV ELVEMO AS.

Where is OLAV ELVEMO AS based?

OLAV ELVEMO AS has its business address in Rykkinn.

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.