biztrac. BETA
COMPANY REGISTER PROFILE
931002902 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

MISJE EIENDOM AS

Org. no. 931002902 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 549,000
Operating profit NOK −60,000
Equity NOK 3.1m
Incorporated 2023
Share capital NOK 3.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).
  • Nylig endring 2026-04-23 Aksjekapital registrert 2026-04-23.

MISJE EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 931002902. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 3.0m, divided into 100000 shares. The company's stated purpose is: “Handel med, drift av og investering i fast eiendom, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 549,000 in revenue and NOK −60,000 in operating profit.

Former names: ATHOMSTART INVEST 838 AS

Key figures · 2025

Revenue
NOK 549,000
▲ +91 %
Operating profit
NOK −60,000
▲ +89 %
Equity
NOK 3.1m
▲ +242 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
3.2%
Weak
Return on total assets
Solidity
10.9%
Satisfactory
Equity as a share of total capital

Who owns MISJE EIENDOM AS?

MISJE EIENDOM AS
NOK 549,000 rev. · NOK −60,000 profit

MISJE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MISJE EIENDOM AS

Who owns MISJE EIENDOM AS?

NIMI II AS is the largest registered owner, with 100.0%.

What is the revenue of MISJE EIENDOM AS?

MISJE EIENDOM AS had revenue of NOK 549,000 in 2025.

Where is MISJE EIENDOM AS based?

MISJE EIENDOM AS has its business address in Bergen.

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.