BIZTRAC BETA
COMPANY REGISTER PROFILE
919778636 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

LUNI INVEST AS

Org. no. 919778636 Limited company (AS) Nesbyen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 3.1m
Equity NOK 8.0m
Incorporated 2017
Share capital NOK 1.0m

LUNI INVEST AS is registered as a limited company in Nesbyen, Buskerud with organisation number 919778636. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering og omsetning av aksjer, eiendom og andre kapitalvarer, samt alt som står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
▲ +61 %
Operating profit
NOK 3.1m
▲ +510 %
Equity
NOK 8.0m
▲ +26 %
Est. value
NOK 9.3m

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
9.6%
Satisfactory
Return on total assets
Solidity
23.0%
Good
Equity as a share of total capital

Who owns LUNI INVEST AS?

LUNI INVEST AS
NOK 6.1m rev. · NOK 3.1m profit

LUNI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUNI INVEST AS own?

LUNI INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUNI INVEST AS

Who owns LUNI INVEST AS?

HALGRIM MITACEK-TØRRISPLASS is the largest registered owner, with 100.0%.

What is the revenue of LUNI INVEST AS?

LUNI INVEST AS had revenue of NOK 6.1m in 2025.

Who is the general manager of LUNI INVEST AS?

Halgrim Mitacek-Tørrisplass is registered as general manager of LUNI INVEST AS.

Where is LUNI INVEST AS based?

LUNI INVEST AS has its business address in Nesbyen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.