BIZTRAC BETA
Buying and selling of own real estate

SKK EIENDOM AS

Org. no. 894613092 Limited company (AS) Indre Østfold Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −76,000
Equity NOK 892,000
Incorporated 2009
Share capital NOK 102,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−76k kr).

SKK EIENDOM AS is registered as a limited company in Indre Østfold, Østfold with organisation number 894613092. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2009. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Kjøp, salg og utleie av egen fast eiendom”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −76,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −76,000
Equity
NOK 892,000
Est. value
NOK 814,000

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.0%
Good
Equity as a share of total capital

Who owns SKK EIENDOM AS?

STIAN SKJØRSHAMMER HOLMEN
SKK EIENDOM AS
NOK 0 rev. · NOK −76,000 profit

SKK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKK EIENDOM AS own?

SKK EIENDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SKK EIENDOM AS

Who owns SKK EIENDOM AS?

STIAN SKJØRSHAMMER HOLMEN is the largest registered owner, with 100.0%.

What is the revenue of SKK EIENDOM AS?

SKK EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of SKK EIENDOM AS?

Stian Skjørshammer Holmen is registered as general manager of SKK EIENDOM AS.

Where is SKK EIENDOM AS based?

SKK EIENDOM AS has its business address in Slitu.

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.