BIZTRAC BETA
Uoppgitt

BANDKASSA HOLDING AS

Org. no. 931342738 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 13,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

BANDKASSA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 931342738. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK 13,000
Est. value
NOK 15,000

Financial health · 2024

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

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

Who owns BANDKASSA HOLDING AS?

GUDMUND OLAVSØNN GUREN
BANDKASSA HOLDING AS
· NOK −12,000 profit

BANDKASSA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BANDKASSA HOLDING AS own?

BANDKASSA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BANDKASSA HOLDING AS

Who owns BANDKASSA HOLDING AS?

GUDMUND OLAVSØNN GUREN is the largest registered owner, with 100.0%.

Who is the general manager of BANDKASSA HOLDING AS?

Gudmund Olavsønn Guren is registered as general manager of BANDKASSA HOLDING AS.

Where is BANDKASSA HOLDING AS based?

BANDKASSA 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.