BIZTRAC BETA
Freight transport by road

LAVIK AS

Org. no. 911576910 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 8.6m
Operating profit NOK 1.8m
Equity NOK 2.7m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-09 Adresseendring registrert 2026-03-09.

LAVIK AS is registered as a limited company in Bergen, Vestland with organisation number 911576910. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av tjenester godstransport på vei, arbeidstjenester knyttet til transport og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.6m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 8.6m
Operating profit
NOK 1.8m
Equity
NOK 2.7m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns LAVIK AS?

JO-STIAN LAVIK
LAVIK AS
NOK 8.6m rev. · NOK 1.8m profit

LAVIK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAVIK AS

Who owns LAVIK AS?

JO-STIAN LAVIK is the largest registered owner, with 67.0%.

What is the revenue of LAVIK AS?

LAVIK AS had revenue of NOK 8.6m in 2024.

Who is the general manager of LAVIK AS?

Cato Andre Lavik is registered as general manager of LAVIK AS.

Where is LAVIK AS based?

LAVIK AS has its business address in Mjølkeråen.

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.