biztrac. BETA
COMPANY REGISTER PROFILE
935588375 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

BEKKESTUA VVS AS

Org. no. 935588375 Limited company (AS) Bærum Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 1.2m
Incorporated 2025
Share capital NOK 80,000

Signals

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

BEKKESTUA VVS AS is registered as a limited company in Bærum, Akershus with organisation number 935588375. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2025. Registered share capital is NOK 80,000, divided into 50 shares. The company's stated purpose is: “Rørleggervirksomhet. Investering i aksjer og andre verdipapirer. Kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 1.2m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns BEKKESTUA VVS AS?

BEKKESTUA VVS AS
NOK 0 rev. · NOK −2,000 profit

BEKKESTUA VVS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BEKKESTUA VVS AS own?

BEKKESTUA VVS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BEKKESTUA VVS AS

Who owns BEKKESTUA VVS AS?

Nicolay Stadsvik is the largest registered owner, with 50.0%.

What is the revenue of BEKKESTUA VVS AS?

BEKKESTUA VVS AS had revenue of NOK 0 in 2025.

Where is BEKKESTUA VVS AS based?

BEKKESTUA VVS AS has its business address in Haslum.

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.