BIZTRAC BETA
Rental and operating of own or leased real estate

BGO PROPERTY AS

Org. no. 918561412 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 200,000
Operating profit NOK 101,000
Equity NOK 2.5m
Incorporated 2017
Share capital NOK 1.6m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BGO PROPERTY AS is registered as a limited company in Bergen, Vestland with organisation number 918561412. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 1.6m, divided into 1470 shares. The company's stated purpose is: “Utvikling, drift, kjøp, salg, utleie av bolig og næringseiendom og hva derved står i sammenheng.”. The most recent filed accounts, for the 2025 financial year, show NOK 200,000 in revenue and NOK 101,000 in operating profit.

Key figures · 2025

Revenue
NOK 200,000
Operating profit
NOK 101,000
Equity
NOK 2.5m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns BGO PROPERTY AS?

SJUSJØ AS
BGO PROPERTY AS
NOK 200,000 rev. · NOK 101,000 profit

BGO PROPERTY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BGO PROPERTY AS

Who owns BGO PROPERTY AS?

SJUSJØ AS is the largest registered owner, with 68.0%.

What is the revenue of BGO PROPERTY AS?

BGO PROPERTY AS had revenue of NOK 200,000 in 2025.

Who is the general manager of BGO PROPERTY AS?

Kristoffer Sjumarken is registered as general manager of BGO PROPERTY AS.

Where is BGO PROPERTY AS based?

BGO PROPERTY AS has its business address in Nesttun.

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.