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

SKAMEK EIENDOM AS

Org. no. 915618731 Limited company (AS) Ålesund Incorporated 2015 Active
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK −75,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−75k kr).

SKAMEK EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 915618731. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
▼ −314 %
Equity
NOK −75,000
▼ −105 %

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
-0.3%
Not satisfactory
Return on total assets
Solidity
-0.6%
Weak
Equity as a share of total capital

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

Who owns SKAMEK EIENDOM AS?

SKAMEK EIENDOM AS
NOK 0 rev. · NOK −38,000 profit

SKAMEK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKAMEK EIENDOM AS

Who owns SKAMEK EIENDOM AS?

SCAN SUPPLIES AS is the largest registered owner, with 100.0%.

What is the revenue of SKAMEK EIENDOM AS?

SKAMEK EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of SKAMEK EIENDOM AS?

Stig Drønnen is registered as general manager of SKAMEK EIENDOM AS.

Where is SKAMEK EIENDOM AS based?

SKAMEK EIENDOM AS has its business address in Ålesund.

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.