BIZTRAC BETA
Rental and operating of own or leased real estate

O.L. SKAHJEM AS

Org. no. 913244451 Limited company (AS) Notodden Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 117,000
Operating profit NOK −614,000
Equity NOK 830,000
Incorporated 2014
Share capital NOK 6.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−614k kr).

O.L. SKAHJEM AS is registered as a limited company in Notodden, Telemark with organisation number 913244451. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 6.0m, divided into 6000 shares. The company's stated purpose is: “Eie, forvalte og leie ut fast eiendom, samt deltagelse i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 117,000 in revenue and NOK −614,000 in operating profit.

Key figures · 2024

Revenue
NOK 117,000
Operating profit
NOK −614,000
Equity
NOK 830,000
Est. value
NOK 757,000

Financial health · 2024

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

Who owns O.L. SKAHJEM AS?

GRO HOWLID ASCHEHOUG
O.L. SKAHJEM AS
NOK 117,000 rev. · NOK −614,000 profit

O.L. SKAHJEM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does O.L. SKAHJEM AS own?

O.L. SKAHJEM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about O.L. SKAHJEM AS

Who owns O.L. SKAHJEM AS?

GRO HOWLID ASCHEHOUG is the largest registered owner, with 100.0%.

What is the revenue of O.L. SKAHJEM AS?

O.L. SKAHJEM AS had revenue of NOK 117,000 in 2024.

Where is O.L. SKAHJEM AS based?

O.L. SKAHJEM AS has its business address in Notodden.

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.