BIZTRAC BETA
Rental and operating of own or leased real estate

STANESVEIEN 35 AS

Org. no. 934402049 Limited company (AS) Bergen Incorporated 1983 Active
Ownership graph ↗
Operating profit NOK −2.1m
Equity NOK 4.0m
Incorporated 1983
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,1 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STANESVEIEN 35 AS is registered as a limited company in Bergen, Vestland with organisation number 934402049. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1983. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Eiendomsbestittelse og hva dermed står i for- bindelse herunder innskudd av kapital og delta i andre virksomheter.”.

Key figures · 2024

Operating profit
NOK −2.1m
Equity
NOK 4.0m
Est. value
NOK 30.0m

Financial health · 2025

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

Who owns STANESVEIEN 35 AS?

CHRISTINE HOLE INVEST AS
STANESVEIEN 35 AS
· NOK −2.1m profit

STANESVEIEN 35 AS has 3 registered shareholders:

All shareholders and roles →

Which companies does STANESVEIEN 35 AS own?

STANESVEIEN 35 AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STANESVEIEN 35 AS

Who owns STANESVEIEN 35 AS?

CHRISTINE HOLE INVEST AS is the largest registered owner, with 33.3%.

Who is the general manager of STANESVEIEN 35 AS?

Endre Hole is registered as general manager of STANESVEIEN 35 AS.

Where is STANESVEIEN 35 AS based?

STANESVEIEN 35 AS has its business address in Bergen.

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.