BIZTRAC BETA
Uoppgitt

SOGNLI HOLDING AS

Org. no. 936128351 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 8.5m
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).
  • Nylig endring 2026-07-10 Aksjekapital registrert 2026-07-10.

SOGNLI HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936128351. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Erverve og eie aksjer og andeler i andre selskaper, handel i finansielle instrumenter samt all annen virksomhet som naturlig hører derved.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 8.5m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns SOGNLI HOLDING AS?

SVEIN OLA SOGNLI
SOGNLI HOLDING AS
NOK 0 rev. · NOK −3,000 profit

SOGNLI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOGNLI HOLDING AS own?

SOGNLI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOGNLI HOLDING AS

Who owns SOGNLI HOLDING AS?

SVEIN OLA SOGNLI is the largest registered owner, with 100.0%.

What is the revenue of SOGNLI HOLDING AS?

SOGNLI HOLDING AS had revenue of NOK 0 in 2025.

Where is SOGNLI HOLDING AS based?

SOGNLI HOLDING AS has its business address in Spongdal.

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.