BIZTRAC BETA
Repair and maintenance of motor vehicles

LARVIK LAST OG BUSS AS

Org. no. 892174512 Limited company (AS) Larvik Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 34.0m
Operating profit NOK 750,000
Equity NOK 8.6m
Incorporated 2008
Employees 15
Share capital NOK 100,000

LARVIK LAST OG BUSS AS is registered as a limited company in Larvik, Vestfold with organisation number 892174512. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel, forhandler av rekvisita, verksted og servicevirksomhet og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 34.0m in revenue and NOK 750,000 in operating profit.

Key figures · 2025

Revenue
NOK 34.0m
Operating profit
NOK 750,000
Equity
NOK 8.6m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns LARVIK LAST OG BUSS AS?

GHM-HOLDING AS
LARVIK LAST OG BUSS AS
NOK 34.0m rev. · NOK 750,000 profit

LARVIK LAST OG BUSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LARVIK LAST OG BUSS AS

Who owns LARVIK LAST OG BUSS AS?

GHM-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LARVIK LAST OG BUSS AS?

LARVIK LAST OG BUSS AS had revenue of NOK 34.0m in 2025.

Who is the general manager of LARVIK LAST OG BUSS AS?

Geir Hansen Moland is registered as general manager of LARVIK LAST OG BUSS AS.

Where is LARVIK LAST OG BUSS AS based?

LARVIK LAST OG BUSS AS has its business address in Larvik.

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.