BIZTRAC BETA
COMPANY REGISTER PROFILE
928652823 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

SIMENS ISBAR DRIFT AS

Org. no. 928652823 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −112,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−112k kr).
  • Nylig endring 2026-06-15 Avregistrert registrert 2026-06-15.

SIMENS ISBAR DRIFT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928652823. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utvikling av matprodukter, herunder produksjon og salg av iskrem, samt utleie av driftsutstyr. Drive cafe og isbar, catering, samt virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −112,000

Financial health · 2024

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

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

Who owns SIMENS ISBAR DRIFT AS?

No shareholders are registered for SIMENS ISBAR DRIFT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SIMENS ISBAR DRIFT AS

What is the revenue of SIMENS ISBAR DRIFT AS?

SIMENS ISBAR DRIFT AS had revenue of NOK 0 in 2024.

Where is SIMENS ISBAR DRIFT AS based?

SIMENS ISBAR DRIFT AS has its business address in Trondheim.

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.