biztrac. BETA
COMPANY REGISTER PROFILE
929476301 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

EIR TEK AS

Org. no. 929476301 Limited company (AS) Sandefjord Incorporated 2022 Active
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK −2,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2k kr).

EIR TEK AS is registered as a limited company in Sandefjord, Vestfold with organisation number 929476301. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eierselskap helseteknologi og innovasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
▼ −78 %
Equity
NOK −2,000
▼ −131 %

Financial health · 2025

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
-61.8%
Not satisfactory
Return on total assets
Solidity
-9.5%
Weak
Equity as a share of total capital

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

Who owns EIR TEK AS?

EIR TEK AS
NOK 0 rev. · NOK −8,000 profit

EIR TEK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIR TEK AS own?

EIR TEK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIR TEK AS

Who owns EIR TEK AS?

Erling Becker Aarseth is the largest registered owner, with 100.0%.

What is the revenue of EIR TEK AS?

EIR TEK AS had revenue of NOK 0 in 2025.

Who is the general manager of EIR TEK AS?

Erling Becker Aarseth is registered as general manager of EIR TEK AS.

Where is EIR TEK AS based?

EIR TEK AS has its business address in Sandefjord.

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

Report a problem

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