BIZTRAC BETA
Rental and operating of own or leased real estate

SOGSTIKOLLEN HOLDING AS

Org. no. 919018461 Limited company (AS) Frogn Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 271,000
Operating profit NOK 16,000
Equity NOK −1.7m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,7 mill kr).

SOGSTIKOLLEN HOLDING AS is registered as a limited company in Frogn, Akershus with organisation number 919018461. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er investering i fast eiendom, eiendomsutleie og alt som står naturlig i forbindelse dermed”. The most recent filed accounts, for the 2025 financial year, show NOK 271,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 271,000
Operating profit
NOK 16,000
Equity
NOK −1.7m
Est. value
NOK 165,000

Financial health · 2025

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

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

Who owns SOGSTIKOLLEN HOLDING AS?

FRODE FAGERLI
SOGSTIKOLLEN HOLDING AS
NOK 271,000 rev. · NOK 16,000 profit

SOGSTIKOLLEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOGSTIKOLLEN HOLDING AS

Who owns SOGSTIKOLLEN HOLDING AS?

FRODE FAGERLI is the largest registered owner, with 100.0%.

What is the revenue of SOGSTIKOLLEN HOLDING AS?

SOGSTIKOLLEN HOLDING AS had revenue of NOK 271,000 in 2025.

Where is SOGSTIKOLLEN HOLDING AS based?

SOGSTIKOLLEN HOLDING AS has its business address in Drøbak.

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.