biztrac. BETA
COMPANY REGISTER PROFILE
930724017 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BSG FORRETNINGER AS

Org. no. 930724017 Limited company (AS) Nesodden Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −121,000
Equity NOK 126,000
Incorporated 2022
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−121k kr).

BSG FORRETNINGER AS is registered as a limited company in Nesodden, Akershus with organisation number 930724017. 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: “Erverve og delta næringsvirksomhet gjennom kjøp og salg av selskapsandeler og/eller kjøp og salg av eiendeler, rettigheter og forpliktelser, samt alt som hermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −121,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −121,000
▼ −12076400 %
Equity
NOK 126,000
▲ +354 %
Est. value
NOK 149,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-128.8%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns BSG FORRETNINGER AS?

BSG FORRETNINGER AS
NOK 0 rev. · NOK −121,000 profit

BSG FORRETNINGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BSG FORRETNINGER AS

Who owns BSG FORRETNINGER AS?

Svein Gulbrandsen is the largest registered owner, with 100.0%.

What is the revenue of BSG FORRETNINGER AS?

BSG FORRETNINGER AS had revenue of NOK 0 in 2025.

Where is BSG FORRETNINGER AS based?

BSG FORRETNINGER AS has its business address in Fagerstrand.

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

Report a problem

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