BIZTRAC BETA
Uoppgitt

TETSU HOLDING AS

Org. no. 927121514 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −216,000
Equity NOK 10.8m
Incorporated 2021
Share capital NOK 663,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−216k kr).

TETSU HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 927121514. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 663,000, divided into 3157 shares. The company's stated purpose is: “Å være holdingselskap, samt delta i andre virksomheter og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −216,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −216,000
Equity
NOK 10.8m
Est. value
NOK 136.4m

Financial health · 2024

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

Who owns TETSU HOLDING AS?

STÅLE OFTEDAL
TETSU HOLDING AS
NOK 0 rev. · NOK −216,000 profit

TETSU HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TETSU HOLDING AS own?

TETSU HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TETSU HOLDING AS

Who owns TETSU HOLDING AS?

STÅLE OFTEDAL is the largest registered owner, with 66.6%.

What is the revenue of TETSU HOLDING AS?

TETSU HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of TETSU HOLDING AS?

Ståle Oftedal is registered as general manager of TETSU HOLDING AS.

Where is TETSU HOLDING AS based?

TETSU HOLDING AS has its business address in Stavanger.

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.