BIZTRAC BETA
Rental and operating of own or leased real estate

NATTEN AS

Org. no. 990012466 Limited company (AS) Nesbyen Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −82,000
Equity NOK 149,000
Incorporated 2006
Share capital NOK 2.0m

Signals

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

NATTEN AS is registered as a limited company in Nesbyen, Buskerud with organisation number 990012466. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 2.0m, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er handelsvirksomhet, kjøp, salg og utleie av fast eiendom, herunder eiendomsutvikling og alt som er i forbindelse med dette herunder deltakelse i selskap med beslektet virksomhet. Selskapets virksomhet omfatter også kjøp og salg av finansaktiva som aksjer og valuta.”.

Key figures · 2025

Operating profit
NOK −82,000
Equity
NOK 149,000
Est. value
NOK 136,000

Financial health · 2025

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

Who owns NATTEN AS?

KNUT TANDBERG
NATTEN AS
· NOK −82,000 profit

NATTEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NATTEN AS own?

NATTEN AS holds stakes in 6 companies:

See the full ownership structure →

Group structure

NATTEN AS er morselskap for 1 datterselskap:

Frequently asked questions about NATTEN AS

Who owns NATTEN AS?

KNUT TANDBERG is the largest registered owner, with 100.0%.

Who is the general manager of NATTEN AS?

Knut Tandberg is registered as general manager of NATTEN AS.

Where is NATTEN AS based?

NATTEN 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 15.06.2026.

Report a problem

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