biztrac. BETA
COMPANY REGISTER PROFILE
933665941 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

SVETRE HOLDING AS

Org. no. 933665941 Limited company (AS) Fredrikstad Incorporated 2024 Active
Operating profit NOK −17,000
Equity NOK −502,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−502k kr).

SVETRE HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 933665941. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å erverve, forvalte og selge aksjer og andre selskapsandeler samt andre holdingeringer, herunder i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −17,000
▼ −615 %
Equity
NOK −502,000
▼ −3351 %

Financial health · 2025

Liquidity
78.60
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1022.7%
Weak
Equity as a share of total capital

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

Who owns SVETRE HOLDING AS?

SVETRE HOLDING AS
· NOK −17,000 profit

SVETRE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVETRE HOLDING AS own?

SVETRE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVETRE HOLDING AS

Who owns SVETRE HOLDING AS?

Sverre Trenum is the largest registered owner, with 100.0%.

Who is the general manager of SVETRE HOLDING AS?

Sverre Trenum is registered as general manager of SVETRE HOLDING AS.

Where is SVETRE HOLDING AS based?

SVETRE HOLDING AS has its business address in Fredrikstad.

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.