BIZTRAC BETA
Other real estate activities on a fee or contract basis

MAKENI AS

Org. no. 921454600 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK 2.2m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MAKENI AS is registered as a limited company in Tromsø, Troms with organisation number 921454600. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, samt tilhørende aktiviteter relatert til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 2.2m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns MAKENI AS?

MADS KENNETH NILSEN
MAKENI AS
NOK 0 rev. · NOK −20,000 profit

MAKENI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAKENI AS own?

MAKENI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MAKENI AS

Who owns MAKENI AS?

MADS KENNETH NILSEN is the largest registered owner, with 100.0%.

What is the revenue of MAKENI AS?

MAKENI AS had revenue of NOK 0 in 2025.

Where is MAKENI AS based?

MAKENI AS has its business address in Kvaløya.

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.