BIZTRAC BETA
Rental and operating of own or leased real estate

SKROG EIENDOM AS

Org. no. 990317569 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −26,000
Equity NOK −11.4m
Incorporated 2006
Share capital NOK 100,000

Signals

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

SKROG EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 990317569. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom, aksjer og verdipapirer og hva hermed står i forbindelse, herunder delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −26,000
Equity
NOK −11.4m

Financial health · 2025

Liquidity
23.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-438.9%
Weak
Equity as a share of total capital

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

Who owns SKROG EIENDOM AS?

MÅLSNES INVEST AS
SKROG EIENDOM AS
· NOK −26,000 profit

SKROG EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does SKROG EIENDOM AS own?

SKROG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKROG EIENDOM AS

Who owns SKROG EIENDOM AS?

MÅLSNES INVEST AS is the largest registered owner, with 31.0%.

Who is the general manager of SKROG EIENDOM AS?

Kolbjørn Jensen is registered as general manager of SKROG EIENDOM AS.

Where is SKROG EIENDOM AS based?

SKROG EIENDOM 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 15.06.2026.

Report a problem

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