BIZTRAC BETA
Freight transport by road

RUNAR BAKKEN AS

Org. no. 988986437 Limited company (AS) Notodden Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −154,000
Equity NOK 55.9m
Incorporated 2005
Share capital NOK 1.8m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−154k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RUNAR BAKKEN AS is registered as a limited company in Notodden, Telemark with organisation number 988986437. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2005. Registered share capital is NOK 1.8m, divided into 594 shares. The company's stated purpose is: “Investerings- og holdingsvirksomhet og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −154,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −154,000
Equity
NOK 55.9m
Est. value
NOK 29.4m

Financial health · 2024

Liquidity
5.48
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
95.2%
Very good
Equity as a share of total capital

Who owns RUNAR BAKKEN AS?

RUNAR BAKKEN
RUNAR BAKKEN AS
NOK 0 rev. · NOK −154,000 profit

RUNAR BAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RUNAR BAKKEN AS own?

RUNAR BAKKEN AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about RUNAR BAKKEN AS

Who owns RUNAR BAKKEN AS?

RUNAR BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of RUNAR BAKKEN AS?

RUNAR BAKKEN AS had revenue of NOK 0 in 2024.

Where is RUNAR BAKKEN AS based?

RUNAR BAKKEN 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.