biztrac. BETA
COMPANY REGISTER PROFILE
924648007 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

ROGALAND EIENDOMSINVEST AS

Org. no. 924648007 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −368,000
Equity NOK −4.7m
Incorporated 2020
Share capital NOK 1.5m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,7 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−368k kr).

ROGALAND EIENDOMSINVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 924648007. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 1.5m, divided into 1500000 shares. The company's stated purpose is: “Kjøp, salg og utvikling av eiendom, investere i andre selskaper, herunder eie aksjer og andre finansielle instrumenter, driver handel med finansielle instrumenter og annen beslektet virksomhet, samt konsulenttjenester.”.

Key figures · 2025

Operating profit
NOK −368,000
▼ −779 %
Equity
NOK −4.7m
▼ −559 %

Financial health · 2025

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
-7.2%
Not satisfactory
Return on total assets
Solidity
-195.2%
Weak
Equity as a share of total capital

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

Who owns ROGALAND EIENDOMSINVEST AS?

ROGALAND EIENDOMSINVEST AS
· NOK −368,000 profit

ROGALAND EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROGALAND EIENDOMSINVEST AS

Who owns ROGALAND EIENDOMSINVEST AS?

T&T HÅLAND HOLDING is the largest registered owner, with 100.0%.

Where is ROGALAND EIENDOMSINVEST AS based?

ROGALAND EIENDOMSINVEST AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.