BIZTRAC BETA
Operation of car parks and garages

AS TORGET PARKERING

Org. no. 859432352 Limited company (AS) Larvik Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 707,000
Equity NOK 6.5m
Incorporated 1990
Share capital NOK 260,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AS TORGET PARKERING is registered as a limited company in Larvik, Vestfold with organisation number 859432352. The business is classified under operation of car parks and garages (NACE 52.212). The company was incorporated in 1990. Registered share capital is NOK 260,000, divided into 130 shares. The company's stated purpose is: “Eie og drift av parkeringshus samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 707,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 707,000
Equity
NOK 6.5m
Est. value
NOK 5.6m

Financial health · 2025

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

Who owns AS TORGET PARKERING?

ALBERT BØE EIENDOM AS
AS TORGET PARKERING
NOK 1.4m rev. · NOK 707,000 profit

AS TORGET PARKERING has 17 registered shareholders:

All shareholders and roles →

Frequently asked questions about AS TORGET PARKERING

Who owns AS TORGET PARKERING?

ALBERT BØE EIENDOM AS is the largest registered owner, with 64.6%.

What is the revenue of AS TORGET PARKERING?

AS TORGET PARKERING had revenue of NOK 1.4m in 2024.

Who is the general manager of AS TORGET PARKERING?

Trygve Bøe is registered as general manager of AS TORGET PARKERING.

Where is AS TORGET PARKERING based?

AS TORGET PARKERING 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.