biztrac. BETA
COMPANY REGISTER PROFILE
989143433 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Leasing of intellectual property and similar products, except copyrighted works

THASSEL AS

Org. no. 989143433 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 8.3m
Incorporated 2005
Share capital NOK 1.0m

Signals

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

THASSEL AS is registered as a limited company in Oslo, Oslo with organisation number 989143433. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investere i aksjer, utvikling og drift av fast eiendom, og ellers delta i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −11,000
▲ +8 %
Equity
NOK 8.3m
▼ −3 %
Est. value
NOK 12.0m

Financial health · 2025

Liquidity
22.48
Very good
Current assets ÷ current liabilities
Profitability
11.6%
Good
Return on total assets
Solidity
98.2%
Very good
Equity as a share of total capital

Who owns THASSEL AS?

THASSEL AS
· NOK −11,000 profit

THASSEL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THASSEL AS own?

THASSEL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about THASSEL AS

Who owns THASSEL AS?

Tor-Egil Hasselstrøm is the largest registered owner, with 100.0%.

Who is the general manager of THASSEL AS?

Tor-Egil Hasselstrøm is registered as general manager of THASSEL AS.

Where is THASSEL AS based?

THASSEL AS has its business address in Oslo.

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.