BIZTRAC BETA
Rental and operating of own or leased real estate

MAUKEN UTVIKLING AS

Org. no. 916339348 Limited company (AS) Målselv Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −30,000
Equity NOK 995,000
Incorporated 2015
Share capital NOK 250,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−30k kr).
  • Nylig endring 2026-03-26 Aksjekapital registrert 2026-03-26.

MAUKEN UTVIKLING AS is registered as a limited company in Målselv, Troms with organisation number 916339348. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 250,000, divided into 800 shares. The company's stated purpose is: “Eie, drive og leie ut eiendom, samt deltakelse i andre selskap, konsulentvirksomhet og annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 995,000
Est. value
NOK 908,000

Financial health · 2025

Liquidity
204.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
94.3%
Very good
Equity as a share of total capital

Who owns MAUKEN UTVIKLING AS?

REIDUN LOVISE TRAASDAHL NILSEN
MAUKEN UTVIKLING AS
NOK 0 rev. · NOK −30,000 profit

MAUKEN UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAUKEN UTVIKLING AS

Who owns MAUKEN UTVIKLING AS?

REIDUN LOVISE TRAASDAHL NILSEN is the largest registered owner, with 75.0%.

What is the revenue of MAUKEN UTVIKLING AS?

MAUKEN UTVIKLING AS had revenue of NOK 0 in 2025.

Where is MAUKEN UTVIKLING AS based?

MAUKEN UTVIKLING AS has its business address in Moen.

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.