BIZTRAC BETA
Public relations and communication activities

LIV LAGA MEDIA AS

Org. no. 935793629 Limited company (AS) Sunnfjord Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 28,000
Operating profit NOK −4,000
Equity NOK 39,000
Incorporated 2025
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

LIV LAGA MEDIA AS is registered as a limited company in Sunnfjord, Vestland with organisation number 935793629. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Tilby freelancejournalistikk, marknadsførings- og kommunikasjonstenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 28,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 28,000
Operating profit
NOK −4,000
Equity
NOK 39,000
Est. value
NOK 48,000

Financial health · 2025

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

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

Who owns LIV LAGA MEDIA AS?

LIV GRIMSBØ
LIV LAGA MEDIA AS
NOK 28,000 rev. · NOK −4,000 profit

LIV LAGA MEDIA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIV LAGA MEDIA AS

Who owns LIV LAGA MEDIA AS?

LIV GRIMSBØ is the largest registered owner, with 75.0%.

What is the revenue of LIV LAGA MEDIA AS?

LIV LAGA MEDIA AS had revenue of NOK 28,000 in 2025.

Who is the general manager of LIV LAGA MEDIA AS?

Liv Grimsbø is registered as general manager of LIV LAGA MEDIA AS.

Where is LIV LAGA MEDIA AS based?

LIV LAGA MEDIA AS has its business address in Førde.

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.