BIZTRAC BETA
COMPANY REGISTER PROFILE
936736262 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SILJE TOPCO AS

Org. no. 936736262 Limited company (AS) Larvik Incorporated 2025 Active
Ownership graph ↗
Equity NOK 45,000
Incorporated 2025
Share capital NOK 361,000

Signals

2 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-12-03.
  • Nylig endring 2026-08-18 Aksjekapital registrert 2026-08-18.

SILJE TOPCO AS is registered as a limited company in Larvik, Vestfold with organisation number 936736262. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 361,000, divided into 45000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper og annen virksomhet som naturlig henger sammen med dette.”.

Key figures · 2025

Equity
NOK 45,000
Est. value
NOK 53,000

Financial health · 2025

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

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

Who owns SILJE TOPCO AS?

SILJE TOPCO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SILJE TOPCO AS

Who owns SILJE TOPCO AS?

SILJE MARGRETHE FØNHUS is the largest registered owner, with 100.0%.

Where is SILJE TOPCO AS based?

SILJE TOPCO AS has its business address in Tjodalyng.

Property

Business address Limveien 4, 3280 Tjodalyng
Cadastral unit 3909-1036/124/0/0
Building Enebolig · 1 unit

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.