BIZTRAC BETA
Legal activities

RUNE VALAKER AS

Org. no. 978666299 Limited company (AS) Bergen Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 561,000
Operating profit NOK −1.8m
Equity NOK 18.1m
Incorporated 1997
Share capital NOK 1.1m

Signals

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

RUNE VALAKER AS is registered as a limited company in Bergen, Vestland with organisation number 978666299. The business is classified under legal activities (NACE 69.100). The company was incorporated in 1997. Registered share capital is NOK 1.1m, divided into 1050 shares. The company's stated purpose is: “Delta med eierandeler i advokatvirksomhet, samt direkte engasjere seg i annen konsulentbistand som ikke er knyttet til rettshjelp, selskapet kan også engasjere seg som medeier i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 561,000 in revenue and NOK −1.8m in operating profit.

Key figures · 2024

Revenue
NOK 561,000
Operating profit
NOK −1.8m
Equity
NOK 18.1m
Est. value
NOK 23.5m

Financial health · 2024

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

Who owns RUNE VALAKER AS?

RUNE VALAKER
RUNE VALAKER AS
NOK 561,000 rev. · NOK −1.8m profit

RUNE VALAKER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RUNE VALAKER AS own?

RUNE VALAKER AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about RUNE VALAKER AS

Who owns RUNE VALAKER AS?

RUNE VALAKER is the largest registered owner, with 100.0%.

What is the revenue of RUNE VALAKER AS?

RUNE VALAKER AS had revenue of NOK 561,000 in 2024.

Where is RUNE VALAKER AS based?

RUNE VALAKER AS has its business address in Bergen.

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.