BIZTRAC BETA
Rental and operating of own or leased real estate

BANKPLASSEN HOLDING AS

Org. no. 932906341 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 352,000
Operating profit NOK −246,000
Equity NOK 5.0m
Incorporated 2024
Share capital NOK 5.0m

Signals

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

BANKPLASSEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 932906341. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 5.0m, divided into 5000 shares. The company's stated purpose is: “Kjøp, utvikling, salg og drift av eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 352,000 in revenue and NOK −246,000 in operating profit.

Key figures · 2024

Revenue
NOK 352,000
Operating profit
NOK −246,000
Equity
NOK 5.0m
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns BANKPLASSEN HOLDING AS?

KILSHOLMEN AS
BANKPLASSEN HOLDING AS
NOK 352,000 rev. · NOK −246,000 profit

BANKPLASSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BANKPLASSEN HOLDING AS er morselskap for 2 datterselskaper:

Frequently asked questions about BANKPLASSEN HOLDING AS

Who owns BANKPLASSEN HOLDING AS?

KILSHOLMEN AS is the largest registered owner, with 100.0%.

What is the revenue of BANKPLASSEN HOLDING AS?

BANKPLASSEN HOLDING AS had revenue of NOK 352,000 in 2024.

Where is BANKPLASSEN HOLDING AS based?

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