BIZTRAC BETA
Rental and operating of own or leased real estate

SVENSEN HOLDING AS

Org. no. 890721362 Limited company (AS) Fredrikstad Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −34,000
Equity NOK 2.3m
Incorporated 2007
Share capital NOK 600,000

Signals

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

SVENSEN HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 890721362. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 600,000, divided into 100 shares. The company's stated purpose is: “Erverv og forvaltning av aksjer og eierandeler i andre foretak, samt investere i fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK 2.3m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns SVENSEN HOLDING AS?

THOMAS ANDRÉ SVENSEN
SVENSEN HOLDING AS
NOK 0 rev. · NOK −34,000 profit

SVENSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVENSEN HOLDING AS own?

SVENSEN HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SVENSEN HOLDING AS

Who owns SVENSEN HOLDING AS?

THOMAS ANDRÉ SVENSEN is the largest registered owner, with 100.0%.

What is the revenue of SVENSEN HOLDING AS?

SVENSEN HOLDING AS had revenue of NOK 0 in 2024.

Where is SVENSEN HOLDING AS based?

SVENSEN HOLDING AS has its business address in Kråkerøy.

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.