BIZTRAC BETA
Buying and selling of own real estate

REVET EIENDOMSINVEST HOLDING AS

Org. no. 927609959 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −157,000
Equity NOK 34.8m
Incorporated 2021
Share capital NOK 30,000

Signals

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

REVET EIENDOMSINVEST HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 927609959. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Investering i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse, herunder å oppta lån for å finansiere virksomheten.”.

Key figures · 2024

Operating profit
NOK −157,000
Equity
NOK 34.8m
Est. value
NOK 31.8m

Financial health · 2024

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

Who owns REVET EIENDOMSINVEST HOLDING AS?

RØYR EIENDOM AS
REVET EIENDOMSINVEST HOLDING AS
· NOK −157,000 profit

REVET EIENDOMSINVEST HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REVET EIENDOMSINVEST HOLDING AS own?

REVET EIENDOMSINVEST HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REVET EIENDOMSINVEST HOLDING AS

Who owns REVET EIENDOMSINVEST HOLDING AS?

RØYR EIENDOM AS is the largest registered owner, with 100.0%.

Where is REVET EIENDOMSINVEST HOLDING AS based?

REVET EIENDOMSINVEST HOLDING AS has its business address in Oslo.

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.