biztrac. BETA
COMPANY REGISTER PROFILE
922412863 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

MESSELT EIENDOM AS

Org. no. 922412863 Limited company (AS) Stor-Elvdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 100,000
Incorporated 2019
Share capital NOK 110,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

MESSELT EIENDOM AS is registered as a limited company in Stor-Elvdal, Innlandet with organisation number 922412863. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 110,000, divided into 1100 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre verdipapirer, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
▼ −4 %
Equity
NOK 100,000
▲ +0 %
Est. value
NOK 69,000

Financial health · 2025

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

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

Who owns MESSELT EIENDOM AS?

MESSELT EIENDOM AS
NOK 0 rev. · NOK −6,000 profit

MESSELT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MESSELT EIENDOM AS

Who owns MESSELT EIENDOM AS?

OSLO BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of MESSELT EIENDOM AS?

MESSELT EIENDOM AS had revenue of NOK 0 in 2025.

Where is MESSELT EIENDOM AS based?

MESSELT EIENDOM AS has its business address in Koppang.

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.