BIZTRAC BETA
Buying and selling of own real estate

TEKNOTOMTEN 3 NÆRING AS

Org. no. 918746935 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −178,000
Equity NOK 37.7m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−178k kr).

TEKNOTOMTEN 3 NÆRING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 918746935. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av egen fast eiendom og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −178,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −178,000
Equity
NOK 37.7m
Est. value
NOK 34.4m

Financial health · 2024

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

Who owns TEKNOTOMTEN 3 NÆRING AS?

TEKNOTOMTEN 3 HOLDING AS
TEKNOTOMTEN 3 NÆRING AS
NOK 0 rev. · NOK −178,000 profit

TEKNOTOMTEN 3 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TEKNOTOMTEN 3 NÆRING AS er morselskap for 56 datterselskaper:

Frequently asked questions about TEKNOTOMTEN 3 NÆRING AS

Who owns TEKNOTOMTEN 3 NÆRING AS?

TEKNOTOMTEN 3 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TEKNOTOMTEN 3 NÆRING AS?

TEKNOTOMTEN 3 NÆRING AS had revenue of NOK 0 in 2024.

Where is TEKNOTOMTEN 3 NÆRING AS based?

TEKNOTOMTEN 3 NÆRING AS has its business address in Heimdal.

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.