BIZTRAC BETA
Rental and operating of own or leased real estate

SLOGEN EIENDOM AS

Org. no. 911619733 Limited company (AS) Ålesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 95,000
Operating profit NOK −128,000
Equity NOK 29,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

SLOGEN EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 911619733. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Erverv av eiendom og interesser i selskap med økonomisk formål, samt annen økonomisk virksomhet og hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 95,000 in revenue and NOK −128,000 in operating profit.

Key figures · 2024

Revenue
NOK 95,000
Operating profit
NOK −128,000
Equity
NOK 29,000
Est. value
NOK 27,000

Financial health · 2024

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

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

Who owns SLOGEN EIENDOM AS?

MØRE ENTREPRENØR HOLDING AS
SLOGEN EIENDOM AS
NOK 95,000 rev. · NOK −128,000 profit

SLOGEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLOGEN EIENDOM AS

Who owns SLOGEN EIENDOM AS?

MØRE ENTREPRENØR HOLDING AS is the largest registered owner, with 66.7%.

What is the revenue of SLOGEN EIENDOM AS?

SLOGEN EIENDOM AS had revenue of NOK 95,000 in 2024.

Where is SLOGEN EIENDOM AS based?

SLOGEN 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 15.06.2026.

Report a problem

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