BIZTRAC BETA
Wholesale of other machinery and equipment

PARKERINGSLØSNINGER AS

Org. no. 922286507 Limited company (AS) Sarpsborg Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 9,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PARKERINGSLØSNINGER AS is registered as a limited company in Sarpsborg, Østfold with organisation number 922286507. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å tilby parkeringsløsninger, parkeringsrelatert utstyr og systemer til det skandinaviske markedet. Samt tjenester, konsultering og service innen samme virksomhetsområdet.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 9,000
Est. value
NOK 11,000

Financial health · 2025

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

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

Who owns PARKERINGSLØSNINGER AS?

AUTODATA AS
PARKERINGSLØSNINGER AS
· NOK −12,000 profit

PARKERINGSLØSNINGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARKERINGSLØSNINGER AS

Who owns PARKERINGSLØSNINGER AS?

AUTODATA AS is the largest registered owner, with 100.0%.

Who is the general manager of PARKERINGSLØSNINGER AS?

Jon Arne Skauen is registered as general manager of PARKERINGSLØSNINGER AS.

Where is PARKERINGSLØSNINGER AS based?

PARKERINGSLØSNINGER AS has its business address in Borgenhaugen.

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.