BIZTRAC BETA
Trade of electricity

BANEVEIEN 32 B AS

Org. no. 993877360 Limited company (AS) Drammen Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −865,000
Incorporated 2009
Share capital NOK 500,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−865k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

BANEVEIEN 32 B AS is registered as a limited company in Drammen, Buskerud with organisation number 993877360. The business is classified under trade of electricity (NACE 35.150). The company was incorporated in 2009. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Handel med elektrisitet og miljøverdier og hva dermed står i forbindelse, kjøp, salg og drift av fast eiendom, samt kjøp av aksjer eller på annen måte delta i annen virksomhet.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK −865,000

Financial health · 2025

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

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

Who owns BANEVEIEN 32 B AS?

SKAHAM INVEST AS
BANEVEIEN 32 B AS
· NOK −5,000 profit

BANEVEIEN 32 B AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BANEVEIEN 32 B AS own?

BANEVEIEN 32 B AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BANEVEIEN 32 B AS

Who owns BANEVEIEN 32 B AS?

SKAHAM INVEST AS is the largest registered owner, with 25.0%.

Who is the general manager of BANEVEIEN 32 B AS?

Pål Gjøstein Søilen is registered as general manager of BANEVEIEN 32 B AS.

Where is BANEVEIEN 32 B AS based?

BANEVEIEN 32 B AS has its business address in Drammen.

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.