BIZTRAC BETA
Repair and maintenance of motor vehicles

LARVIK LAST & BILPÅBYGG AS

Org. no. 931272136 Limited company (AS) Larvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 1.1m
Equity NOK 1.7m
Incorporated 2023
Employees 5
Share capital NOK 100,000

LARVIK LAST & BILPÅBYGG AS is registered as a limited company in Larvik, Vestfold with organisation number 931272136. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Reparasjon og ombygging av motorkjøretøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 1.1m
Equity
NOK 1.7m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns LARVIK LAST & BILPÅBYGG AS?

GILLER & SØNN SVEIS & REP AS
LARVIK LAST & BILPÅBYGG AS
NOK 3.4m rev. · NOK 1.1m profit

LARVIK LAST & BILPÅBYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LARVIK LAST & BILPÅBYGG AS

Who owns LARVIK LAST & BILPÅBYGG AS?

GILLER & SØNN SVEIS & REP AS is the largest registered owner, with 67.0%.

What is the revenue of LARVIK LAST & BILPÅBYGG AS?

LARVIK LAST & BILPÅBYGG AS had revenue of NOK 3.4m in 2025.

Who is the general manager of LARVIK LAST & BILPÅBYGG AS?

Bjørnar Giller is registered as general manager of LARVIK LAST & BILPÅBYGG AS.

Where is LARVIK LAST & BILPÅBYGG AS based?

LARVIK LAST & BILPÅBYGG 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.