BIZTRAC BETA
Other services incidental to land transport n.e.c.

LARVIK PUTEBILTJENESTE AS

Org. no. 931921150 Limited company (AS) Larvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 253,000
Equity NOK 701,000
Incorporated 2023
Share capital NOK 100,000

LARVIK PUTEBILTJENESTE AS is registered as a limited company in Larvik, Vestfold with organisation number 931921150. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 4 shares. The company's stated purpose is: “Putebiltjeneste og arbeidsvarsling og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 253,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 253,000
Equity
NOK 701,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.8%
Good
Equity as a share of total capital

Who owns LARVIK PUTEBILTJENESTE AS?

LEIF ERIK NILSEN
LARVIK PUTEBILTJENESTE AS
NOK 6.3m rev. · NOK 253,000 profit

LARVIK PUTEBILTJENESTE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LARVIK PUTEBILTJENESTE AS

Who owns LARVIK PUTEBILTJENESTE AS?

LEIF ERIK NILSEN is the largest registered owner, with 25.0%.

What is the revenue of LARVIK PUTEBILTJENESTE AS?

LARVIK PUTEBILTJENESTE AS had revenue of NOK 6.3m in 2025.

Who is the general manager of LARVIK PUTEBILTJENESTE AS?

Leif Erik Nilsen is registered as general manager of LARVIK PUTEBILTJENESTE AS.

Where is LARVIK PUTEBILTJENESTE AS based?

LARVIK PUTEBILTJENESTE 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.