biztrac. BETA
COMPANY REGISTER PROFILE
928605167 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

MJÅVANNSVEGEN 42 AS

Org. no. 928605167 Limited company (AS) Kristiansand Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 422,000
Operating profit NOK 281,000
Equity NOK 1,000
Incorporated 2021
Share capital NOK 30,000

MJÅVANNSVEGEN 42 AS is registered as a limited company in Kristiansand, Agder with organisation number 928605167. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og forvalting av fast eiendom og alt som står i naturlig forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 422,000 in revenue and NOK 281,000 in operating profit.

Former names: REAR INVEST AS

Key figures · 2025

Revenue
NOK 422,000
Operating profit
NOK 281,000
▲ +3268 %
Equity
NOK 1,000
▲ +108 %
Est. value
NOK 263,000

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
6.0%
Weak
Return on total assets
Solidity
0.0%
Weak
Equity as a share of total capital

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

Who owns MJÅVANNSVEGEN 42 AS?

MJÅVANNSVEGEN 42 AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MJÅVANNSVEGEN 42 AS

Who owns MJÅVANNSVEGEN 42 AS?

NICOS HOLDING AS is the largest registered owner, with 34.0%.

What is the revenue of MJÅVANNSVEGEN 42 AS?

MJÅVANNSVEGEN 42 AS had revenue of NOK 422,000 in 2025.

Where is MJÅVANNSVEGEN 42 AS based?

MJÅVANNSVEGEN 42 AS has its business address in Kristiansand S.

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.