BIZTRAC BETA
Uoppgitt

BIMME HOLDING AS

Org. no. 928823172 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 1.0m
Incorporated 2022
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

BIMME HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 928823172. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Eie og forvalte fast eiendom og aksjer samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 1.0m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns BIMME HOLDING AS?

VIKTOR LØSCH DANNEBORG
BIMME HOLDING AS
NOK 0 rev. · NOK −13,000 profit

BIMME HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BIMME HOLDING AS own?

BIMME HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BIMME HOLDING AS

Who owns BIMME HOLDING AS?

VIKTOR LØSCH DANNEBORG is the largest registered owner, with 100.0%.

What is the revenue of BIMME HOLDING AS?

BIMME HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of BIMME HOLDING AS?

Viktor Løsch Danneborg is registered as general manager of BIMME HOLDING AS.

Where is BIMME HOLDING AS based?

BIMME HOLDING AS has its business address in Oslo.

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.