BIZTRAC BETA
Sports and recreation education

LIVAK AS

Org. no. 930069280 Limited company (AS) Kristiansund Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 353,000
Operating profit NOK −69,000
Equity NOK −51,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−51k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−69k kr).

LIVAK AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 930069280. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenesteleveranser innen helse og trening samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 353,000 in revenue and NOK −69,000 in operating profit.

Key figures · 2024

Revenue
NOK 353,000
Operating profit
NOK −69,000
Equity
NOK −51,000

Financial health · 2024

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-164.1%
Weak
Equity as a share of total capital

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

Who owns LIVAK AS?

HÅVARD SÆTERØY RØDAHL
LIVAK AS
NOK 353,000 rev. · NOK −69,000 profit

LIVAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIVAK AS

Who owns LIVAK AS?

HÅVARD SÆTERØY RØDAHL is the largest registered owner, with 100.0%.

What is the revenue of LIVAK AS?

LIVAK AS had revenue of NOK 353,000 in 2024.

Who is the general manager of LIVAK AS?

Håvard Sæterøy Rødahl is registered as general manager of LIVAK AS.

Where is LIVAK AS based?

LIVAK AS has its business address in Kristiansund N.

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.