BIZTRAC BETA
Other technical consultancy

TECNORACE AS

Org. no. 920624081 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 133,000
Operating profit NOK −421,000
Equity NOK −2.7m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−421k kr).

TECNORACE AS is registered as a limited company in Bærum, Akershus with organisation number 920624081. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000000 shares. The company's stated purpose is: “Utvikle undervandsroboter, salg av kjemi produkter og grave/måke tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 133,000 in revenue and NOK −421,000 in operating profit.

Key figures · 2024

Revenue
NOK 133,000
Operating profit
NOK −421,000
Equity
NOK −2.7m

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-518.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TECNORACE AS?

MILESTONE HOLDING AS
TECNORACE AS
NOK 133,000 rev. · NOK −421,000 profit

TECNORACE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TECNORACE AS

Who owns TECNORACE AS?

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

What is the revenue of TECNORACE AS?

TECNORACE AS had revenue of NOK 133,000 in 2024.

Who is the general manager of TECNORACE AS?

Trond Sivertsen is registered as general manager of TECNORACE AS.

Where is TECNORACE AS based?

TECNORACE AS has its business address in Bekkestua.

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.