BIZTRAC BETA
Operation of car parks and garages

SLUPPEN PARKERING AS

Org. no. 919006684 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 14.3m
Operating profit NOK 5.8m
Equity NOK 210,000
Incorporated 2017
Share capital NOK 100,000

Signals

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

SLUPPEN PARKERING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 919006684. The business is classified under operation of car parks and garages (NACE 52.212). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Administrere og forvalte annens fast eiendom for utleie, herunder utleie av eiendom i parkeringsvirksomhet, samt annen beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.3m in revenue and NOK 5.8m in operating profit.

Key figures · 2024

Revenue
NOK 14.3m
Operating profit
NOK 5.8m
Equity
NOK 210,000
Est. value
NOK 15.9m

Financial health · 2024

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.9%
Not satisfactory
Equity as a share of total capital

Who owns SLUPPEN PARKERING AS?

R KJELDSBERG AS
SLUPPEN PARKERING AS
NOK 14.3m rev. · NOK 5.8m profit

SLUPPEN PARKERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLUPPEN PARKERING AS

Who owns SLUPPEN PARKERING AS?

R KJELDSBERG AS is the largest registered owner, with 100.0%.

What is the revenue of SLUPPEN PARKERING AS?

SLUPPEN PARKERING AS had revenue of NOK 14.3m in 2024.

Where is SLUPPEN PARKERING AS based?

SLUPPEN PARKERING AS has its business address in Trondheim.

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.