BIZTRAC BETA
Operation of car parks and garages

BODØ SENTRUMSPARKERING AS

Org. no. 920803474 Limited company (AS) Bodø Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 461,000
Operating profit NOK 389,000
Equity NOK −408,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−408k kr).

BODØ SENTRUMSPARKERING AS is registered as a limited company in Bodø, Nordland with organisation number 920803474. The business is classified under operation of car parks and garages (NACE 52.212). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Erverv, utvikling og utleie av parkeringsplasser i parkeringsvirksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 461,000 in revenue and NOK 389,000 in operating profit.

Key figures · 2025

Revenue
NOK 461,000
Operating profit
NOK 389,000
Equity
NOK −408,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BODØ SENTRUMSPARKERING AS?

VIFIRE AS
BODØ SENTRUMSPARKERING AS
NOK 461,000 rev. · NOK 389,000 profit

BODØ SENTRUMSPARKERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BODØ SENTRUMSPARKERING AS

Who owns BODØ SENTRUMSPARKERING AS?

VIFIRE AS is the largest registered owner, with 60.0%.

What is the revenue of BODØ SENTRUMSPARKERING AS?

BODØ SENTRUMSPARKERING AS had revenue of NOK 461,000 in 2025.

Where is BODØ SENTRUMSPARKERING AS based?

BODØ SENTRUMSPARKERING AS has its business address in Bodø.

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.