BIZTRAC BETA
Wholesale of other machinery and equipment

EMITECH AS

Org. no. 968115979 Limited company (AS) Larvik Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 15.5m
Operating profit NOK 1.3m
Equity NOK 2.4m
Incorporated 1993
Share capital NOK 2.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EMITECH AS is registered as a limited company in Larvik, Vestfold with organisation number 968115979. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1993. Registered share capital is NOK 2.0m, divided into 13033 shares. The company's stated purpose is: “Utvikle, markedsføre, selge og servicere tekniske kvalitetsprodukter og løsninger med fokus innenfor sikkerhet og miljø, herunder deltakelse i andre selskapet relatert til samme.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 15.5m
Operating profit
NOK 1.3m
Equity
NOK 2.4m
Est. value
NOK 5.8m

Financial health · 2025

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

Who owns EMITECH AS?

ELVESTAD AS
EMITECH AS
NOK 15.5m rev. · NOK 1.3m profit

EMITECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EMITECH AS

Who owns EMITECH AS?

ELVESTAD AS is the largest registered owner, with 100.0%.

What is the revenue of EMITECH AS?

EMITECH AS had revenue of NOK 15.5m in 2025.

Who is the general manager of EMITECH AS?

Tore Erland Gregersen is registered as general manager of EMITECH AS.

Where is EMITECH AS based?

EMITECH AS has its business address in Helgeroa.

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.