BIZTRAC BETA
Rental and operating of own or leased real estate

RAVNKLOBAKKEN AS

Org. no. 999608590 Limited company (AS) Trondheim Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 602,000
Operating profit NOK −101,000
Equity NOK 813,000
Incorporated 2013
Share capital NOK 50,000

Signals

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

RAVNKLOBAKKEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 999608590. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Drive med faste eiendom, herunder utvikling og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 602,000 in revenue and NOK −101,000 in operating profit.

Key figures · 2024

Revenue
NOK 602,000
Operating profit
NOK −101,000
Equity
NOK 813,000
Est. value
NOK 692,000

Financial health · 2025

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

Who owns RAVNKLOBAKKEN AS?

PPM PROSJEKT TRONDHEIM AS
RAVNKLOBAKKEN AS
NOK 602,000 rev. · NOK −101,000 profit

RAVNKLOBAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAVNKLOBAKKEN AS

Who owns RAVNKLOBAKKEN AS?

PPM PROSJEKT TRONDHEIM AS is the largest registered owner, with 100.0%.

What is the revenue of RAVNKLOBAKKEN AS?

RAVNKLOBAKKEN AS had revenue of NOK 602,000 in 2024.

Where is RAVNKLOBAKKEN AS based?

RAVNKLOBAKKEN 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.