BIZTRAC BETA
Rental and operating of own or leased real estate

RÅDGIVERGÅRDEN AS

Org. no. 927434067 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 2.9m
Equity NOK 16.2m
Incorporated 2021
Share capital NOK 16.1m

Signals

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

RÅDGIVERGÅRDEN AS is registered as a limited company in Bergen, Vestland with organisation number 927434067. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 16.1m, divided into 100 shares. The company's stated purpose is: “Eie, forvalte og drive forretningseiendommen gnr. 22, bnr. 612 i Bergen kommune, samt eventuell annen eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 2.9m
Equity
NOK 16.2m
Est. value
NOK 18.0m

Financial health · 2024

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

Who owns RÅDGIVERGÅRDEN AS?

SPELHAUGEN NÆRINGSPARK AS
RÅDGIVERGÅRDEN AS
NOK 4.2m rev. · NOK 2.9m profit

RÅDGIVERGÅRDEN AS has 2 registered shareholders:

All shareholders and roles →

Group structure

RÅDGIVERGÅRDEN AS er morselskap for 11 datterselskaper:

Frequently asked questions about RÅDGIVERGÅRDEN AS

Who owns RÅDGIVERGÅRDEN AS?

SPELHAUGEN NÆRINGSPARK AS is the largest registered owner, with 99.0%.

What is the revenue of RÅDGIVERGÅRDEN AS?

RÅDGIVERGÅRDEN AS had revenue of NOK 4.2m in 2024.

Where is RÅDGIVERGÅRDEN AS based?

RÅDGIVERGÅRDEN AS has its business address in Bergen.

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.