BIZTRAC BETA
COMPANY REGISTER PROFILE
931432087 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 02.09.2026
BONPOINT INVEST AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

BONPOINT INVEST AS

Org. no. 931432087 Limited company (AS) Oslo Incorporated 2023 In liquidation
Ownership graph ↗
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

BONPOINT INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 931432087. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Personlige investeringer.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 30,000

Financial health · 2025

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

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

Who owns BONPOINT INVEST AS?

BONPOINT INVEST AS
· NOK 0 profit

BONPOINT INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BONPOINT INVEST AS

Who owns BONPOINT INVEST AS?

PETER RIISE FROGNER is the largest registered owner, with 100.0%.

Where is BONPOINT INVEST AS based?

BONPOINT INVEST AS has its business address in Oslo.

Property

Business address Konventveien 3B, 0377 Oslo
Cadastral unit 301-32/68/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.