BIZTRAC BETA
Ventilation installation

TEVAS AS

Org. no. 982715199 Limited company (AS) Bergen Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 28.1m
Operating profit NOK −4.6m
Equity NOK 3.9m
Incorporated 2000
Employees 13
Share capital NOK 1.3m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,6 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TEVAS AS is registered as a limited company in Bergen, Vestland with organisation number 982715199. The business is classified under ventilation installation (NACE 43.223). The company was incorporated in 2000 and has 13 registered employees. Registered share capital is NOK 1.3m, divided into 11720 shares. The company's stated purpose is: “Levere tekniske totalentrepriser, både prosjekterende og utførende, til tiltakshavere og andre sentrale aktører innen byggebransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.1m in revenue and NOK −4.6m in operating profit.

Key figures · 2024

Revenue
NOK 28.1m
Operating profit
NOK −4.6m
Equity
NOK 3.9m
Est. value
NOK 11.4m

Financial health · 2024

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.8%
Good
Equity as a share of total capital

Who owns TEVAS AS?

ALLIER AS
TEVAS AS
NOK 28.1m rev. · NOK −4.6m profit

TEVAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEVAS AS

Who owns TEVAS AS?

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

What is the revenue of TEVAS AS?

TEVAS AS had revenue of NOK 28.1m in 2024.

Who is the general manager of TEVAS AS?

Eirik Fossmark Hopp is registered as general manager of TEVAS AS.

Where is TEVAS AS based?

TEVAS AS has its business address in Nesttun.

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.