BIZTRAC BETA
Rental and operating of own or leased real estate

RANHEIM PARKERING AS

Org. no. 925388920 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −23,000
Equity NOK 19.9m
Incorporated 2020
Share capital NOK 3.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).

RANHEIM PARKERING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925388920. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 3.0m, divided into 30000 shares. The company's stated purpose is: “Utbygging og drift av parkeringsanlegg og det som står i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −23,000
Equity
NOK 19.9m
Est. value
NOK 14.5m

Financial health · 2025

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

Who owns RANHEIM PARKERING AS?

RANHEIM IDRETTSLAG
RANHEIM PARKERING AS
NOK 1.2m rev. · NOK −23,000 profit

RANHEIM PARKERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RANHEIM PARKERING AS

Who owns RANHEIM PARKERING AS?

RANHEIM IDRETTSLAG is the largest registered owner, with 50.0%.

What is the revenue of RANHEIM PARKERING AS?

RANHEIM PARKERING AS had revenue of NOK 1.2m in 2025.

Who is the general manager of RANHEIM PARKERING AS?

Torgrim Olsen is registered as general manager of RANHEIM PARKERING AS.

Where is RANHEIM PARKERING AS based?

RANHEIM PARKERING AS has its business address in Ranheim.

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.