BIZTRAC BETA
Buying and selling of own real estate

BSG HOLDING AS

Org. no. 913395409 Limited company (AS) Enebakk Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 753,000
Operating profit NOK 37,000
Equity NOK −179,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−179k kr).

BSG HOLDING AS is registered as a limited company in Enebakk, Akershus with organisation number 913395409. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av verdipapirer og eiendom og alt som står i naturlig forbindelse med det.”. The most recent filed accounts, for the 2025 financial year, show NOK 753,000 in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 753,000
Operating profit
NOK 37,000
Equity
NOK −179,000
Est. value
NOK 506,000

Financial health · 2025

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

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

Who owns BSG HOLDING AS?

MARIUS GJEVIK
BSG HOLDING AS
NOK 753,000 rev. · NOK 37,000 profit

BSG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BSG HOLDING AS own?

BSG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BSG HOLDING AS

Who owns BSG HOLDING AS?

MARIUS GJEVIK is the largest registered owner, with 100.0%.

What is the revenue of BSG HOLDING AS?

BSG HOLDING AS had revenue of NOK 753,000 in 2025.

Where is BSG HOLDING AS based?

BSG HOLDING AS has its business address in Ytre Enebakk.

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.