BIZTRAC BETA
Repair and maintenance of motor vehicles

TETT AS

Org. no. 989188704 Limited company (AS) Asker Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK −1.7m
Equity NOK 77.5m
Incorporated 2005
Share capital NOK 800,000

Signals

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

TETT AS is registered as a limited company in Asker, Akershus with organisation number 989188704. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2005. Registered share capital is NOK 800,000, divided into 10000 shares. The company's stated purpose is: “Selskapet har til formål å investere i andre selskaper, verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK −1.7m
Equity
NOK 77.5m
Est. value
NOK 76.5m

Financial health · 2024

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

Who owns TETT AS?

TONJE HAUG
TETT AS
NOK 3.4m rev. · NOK −1.7m profit

TETT AS has 6 registered shareholders:

All shareholders and roles →

Which companies does TETT AS own?

TETT AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

TETT AS er morselskap for 10 datterselskaper:

Frequently asked questions about TETT AS

Who owns TETT AS?

TONJE HAUG is the largest registered owner, with 21.6%.

What is the revenue of TETT AS?

TETT AS had revenue of NOK 3.4m in 2024.

Where is TETT AS based?

TETT AS has its business address in Nesbru.

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.