BIZTRAC BETA
Business and other management consultancy activities

SOMMERN KOMMER AS

Org. no. 919728108 Limited company (AS) Nes Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK −44,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−44k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).

SOMMERN KOMMER AS is registered as a limited company in Nes, Akershus with organisation number 919728108. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Import av varer, investering i hester, aksjer, verdipapirer, fast eiendom, drift av hoteller og restauranter, shipping m.v., kjøp og salg av biler, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −8,000
Equity
NOK −44,000

Financial health · 2024

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

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

Who owns SOMMERN KOMMER AS?

NICOLAI RADMER NIELSEN
SOMMERN KOMMER AS
· NOK −8,000 profit

SOMMERN KOMMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOMMERN KOMMER AS

Who owns SOMMERN KOMMER AS?

NICOLAI RADMER NIELSEN is the largest registered owner, with 100.0%.

Who is the general manager of SOMMERN KOMMER AS?

Nicolai Radmer Nielsen is registered as general manager of SOMMERN KOMMER AS.

Where is SOMMERN KOMMER AS based?

SOMMERN KOMMER AS has its business address in Vormsund.

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.