BIZTRAC BETA
Civil engineering activities

TJUVREDD HOLDING AS

Org. no. 932590441 Limited company (AS) Indre Østfold Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 98,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

TJUVREDD HOLDING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 932590441. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å investere og forvalte investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 98,000
Est. value
NOK 23.7m

Financial health · 2025

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

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

Who owns TJUVREDD HOLDING AS?

STEIN ARNE BRANDSØY MEIER
TJUVREDD HOLDING AS
NOK 0 rev. · NOK −26,000 profit

TJUVREDD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TJUVREDD HOLDING AS own?

TJUVREDD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TJUVREDD HOLDING AS

Who owns TJUVREDD HOLDING AS?

STEIN ARNE BRANDSØY MEIER is the largest registered owner, with 100.0%.

What is the revenue of TJUVREDD HOLDING AS?

TJUVREDD HOLDING AS had revenue of NOK 0 in 2025.

Where is TJUVREDD HOLDING AS based?

TJUVREDD HOLDING AS has its business address in Knapstad.

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.