BIZTRAC BETA
Rental and operating of own or leased real estate

DANIEL INVEST AS

Org. no. 998033365 Limited company (AS) Lillehammer Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −83,000
Equity NOK 23.0m
Incorporated 2012
Share capital NOK 158,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−83k kr).

DANIEL INVEST AS is registered as a limited company in Lillehammer, Innlandet with organisation number 998033365. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 158,000, divided into 31500 shares. The company's stated purpose is: “Å eie aksjer og selskapsandeler i andre selskaper og investerer i alle former for form finansaktiva samt fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −83,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −83,000
Equity
NOK 23.0m
Est. value
NOK 21.1m

Financial health · 2025

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

Who owns DANIEL INVEST AS?

JON DANIELSEN AARHUS
DANIEL INVEST AS
NOK 0 rev. · NOK −83,000 profit

DANIEL INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does DANIEL INVEST AS own?

DANIEL INVEST AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about DANIEL INVEST AS

Who owns DANIEL INVEST AS?

JON DANIELSEN AARHUS is the largest registered owner, with 90.0%.

What is the revenue of DANIEL INVEST AS?

DANIEL INVEST AS had revenue of NOK 0 in 2025.

Where is DANIEL INVEST AS based?

DANIEL INVEST AS has its business address in Lillehammer.

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.