BIZTRAC BETA
Rental and operating of own or leased real estate

SLEMMEN EIENDOM AS

Org. no. 991851402 Limited company (AS) Rauma Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 75,000
Operating profit NOK 5,000
Equity NOK 34,000
Incorporated 2007
Share capital NOK 100,000

SLEMMEN EIENDOM AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 991851402. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er kjøp og salg av fast eiendom samt utvikling og utleie av fast eiendom, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 75,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 75,000
Operating profit
NOK 5,000
Equity
NOK 34,000
Est. value
NOK 37,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.3%
Weak
Equity as a share of total capital

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

Who owns SLEMMEN EIENDOM AS?

ANDERS SLEMMEN
SLEMMEN EIENDOM AS
NOK 75,000 rev. · NOK 5,000 profit

SLEMMEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLEMMEN EIENDOM AS

Who owns SLEMMEN EIENDOM AS?

ANDERS SLEMMEN is the largest registered owner, with 50.0%.

What is the revenue of SLEMMEN EIENDOM AS?

SLEMMEN EIENDOM AS had revenue of NOK 75,000 in 2025.

Who is the general manager of SLEMMEN EIENDOM AS?

Alf Inge Slemmen is registered as general manager of SLEMMEN EIENDOM AS.

Where is SLEMMEN EIENDOM AS based?

SLEMMEN EIENDOM AS has its business address in Åfarnes.

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.