BIZTRAC BETA
Other captive investment companies

THYRI KRAFT AS

Org. no. 913417356 Limited company (AS) Lærdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4,000
Equity NOK 42,000
Incorporated 2014
Share capital NOK 81,000

Signals

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

THYRI KRAFT AS is registered as a limited company in Lærdal, Vestland with organisation number 913417356. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 81,000, divided into 805 shares. The company's stated purpose is: “Investering og forvaltning av andre selskaper og eiendommer, samt produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 42,000
Est. value
NOK 39,000

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns THYRI KRAFT AS?

HANS INGE THYRI
THYRI KRAFT AS
NOK 0 rev. · NOK −4,000 profit

THYRI KRAFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about THYRI KRAFT AS

Who owns THYRI KRAFT AS?

HANS INGE THYRI is the largest registered owner, with 85.1%.

What is the revenue of THYRI KRAFT AS?

THYRI KRAFT AS had revenue of NOK 0 in 2024.

Where is THYRI KRAFT AS based?

THYRI KRAFT AS has its business address in Lærdal.

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.