BIZTRAC BETA
Support services to forestry

HASÅS TYNNINGSLAG AS

Org. no. 936225748 Limited company (AS) Sandefjord Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 137,000
Operating profit NOK −209,000
Equity NOK 1.7m
Incorporated 2025
Share capital NOK 400,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−209k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-08-21.

HASÅS TYNNINGSLAG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 936225748. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2025. Registered share capital is NOK 400,000, divided into 100 shares. The company's stated purpose is: “Tjenester tilknyttet skogbruk.”. The most recent filed accounts, for the 2025 financial year, show NOK 137,000 in revenue and NOK −209,000 in operating profit.

Key figures · 2025

Revenue
NOK 137,000
Operating profit
NOK −209,000
Equity
NOK 1.7m
Est. value
NOK 903,000

Financial health · 2025

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

Who owns HASÅS TYNNINGSLAG AS?

KØRPEN HOLDING AS
HASÅS TYNNINGSLAG AS
NOK 137,000 rev. · NOK −209,000 profit

HASÅS TYNNINGSLAG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HASÅS TYNNINGSLAG AS

Who owns HASÅS TYNNINGSLAG AS?

KØRPEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of HASÅS TYNNINGSLAG AS?

HASÅS TYNNINGSLAG AS had revenue of NOK 137,000 in 2025.

Who is the general manager of HASÅS TYNNINGSLAG AS?

Kristian Hasås is registered as general manager of HASÅS TYNNINGSLAG AS.

Where is HASÅS TYNNINGSLAG AS based?

HASÅS TYNNINGSLAG AS has its business address in Kodal.

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.