BIZTRAC BETA
Business and other management consultancy activities

SMEG EIENDOM AS

Org. no. 927032635 Limited company (AS) Ringerike Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK −35,000
Operating profit NOK −46,000
Equity NOK −178,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−178k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

SMEG EIENDOM AS is registered as a limited company in Ringerike, Buskerud with organisation number 927032635. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rådgivning, samt investering i eiendommer, eiendomsselskaper og deltakelse i andre tilsvarende selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK −35,000 in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK −35,000
Operating profit
NOK −46,000
Equity
NOK −178,000

Financial health · 2024

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

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

Who owns SMEG EIENDOM AS?

RAIS UTVIKLING AS
SMEG EIENDOM AS
NOK −35,000 rev. · NOK −46,000 profit

SMEG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMEG EIENDOM AS

Who owns SMEG EIENDOM AS?

RAIS UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of SMEG EIENDOM AS?

SMEG EIENDOM AS had revenue of NOK −35,000 in 2024.

Where is SMEG EIENDOM AS based?

SMEG EIENDOM AS has its business address in Hønefoss.

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.