biztrac. BETA
COMPANY REGISTER PROFILE
922172552 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SURESOKKE AS

Org. no. 922172552 Limited company (AS) Lom Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −112,000
Equity NOK −219,000
Incorporated 2019
Share capital NOK 282,000

Signals

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

SURESOKKE AS is registered as a limited company in Lom, Innlandet with organisation number 922172552. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 282,000, divided into 300 shares. The company's stated purpose is: “Investere i andre selskap. Salg og markedsføring av tjenester og produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −112,000 in operating profit.

Former names: ESPEN KOLDEN AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −112,000
▼ −6 %
Equity
NOK −219,000
▼ −247 %

Financial health · 2025

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
-51.0%
Not satisfactory
Return on total assets
Solidity
-110.2%
Weak
Equity as a share of total capital

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

Who owns SURESOKKE AS?

SURESOKKE AS
NOK 0 rev. · NOK −112,000 profit

SURESOKKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SURESOKKE AS own?

SURESOKKE AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about SURESOKKE AS

Who owns SURESOKKE AS?

Espen Kolden is the largest registered owner, with 100.0%.

What is the revenue of SURESOKKE AS?

SURESOKKE AS had revenue of NOK 0 in 2025.

Where is SURESOKKE AS based?

SURESOKKE AS has its business address in Lom.

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.