BIZTRAC BETA
Retail sale of cultural and recreational goods n.e.c.

LIVET ER KORT AS

Org. no. 828005952 Limited company (AS) Sveio Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 594,000
Operating profit NOK 58,000
Equity NOK −31,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

LIVET ER KORT AS is registered as a limited company in Sveio, Vestland with organisation number 828005952. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Import og salg av samlekort, sportsartikler, og alt som omhandler dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 594,000 in revenue and NOK 58,000 in operating profit.

Key figures · 2024

Revenue
NOK 594,000
Operating profit
NOK 58,000
Equity
NOK −31,000
Est. value
NOK 304,000

Financial health · 2024

Liquidity
2.57
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-35.1%
Weak
Equity as a share of total capital

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

Who owns LIVET ER KORT AS?

MALVIN MUNTHE
LIVET ER KORT AS
NOK 594,000 rev. · NOK 58,000 profit

LIVET ER KORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIVET ER KORT AS

Who owns LIVET ER KORT AS?

MALVIN MUNTHE is the largest registered owner, with 50.0%.

What is the revenue of LIVET ER KORT AS?

LIVET ER KORT AS had revenue of NOK 594,000 in 2024.

Who is the general manager of LIVET ER KORT AS?

Malvin Munthe is registered as general manager of LIVET ER KORT AS.

Where is LIVET ER KORT AS based?

LIVET ER KORT AS has its business address in Sveio.

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.