BIZTRAC BETA
Rental and operating of own or leased real estate

BNE SKI VESTVEIEN AS

Org. no. 921367813 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 808,000
Operating profit NOK 799,000
Equity NOK 1.2m
Incorporated 2018
Share capital NOK 149,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BNE SKI VESTVEIEN AS is registered as a limited company in Oslo, Oslo with organisation number 921367813. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 149,000, divided into 148897 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse, herunder deltagelse i øvrige selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 808,000 in revenue and NOK 799,000 in operating profit.

Key figures · 2025

Revenue
NOK 808,000
Operating profit
NOK 799,000
Equity
NOK 1.2m
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.6%
Not satisfactory
Equity as a share of total capital

Who owns BNE SKI VESTVEIEN AS?

BANE NOR EIENDOM AS
BNE SKI VESTVEIEN AS
NOK 808,000 rev. · NOK 799,000 profit

BNE SKI VESTVEIEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BNE SKI VESTVEIEN AS

Who owns BNE SKI VESTVEIEN AS?

BANE NOR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BNE SKI VESTVEIEN AS?

BNE SKI VESTVEIEN AS had revenue of NOK 808,000 in 2025.

Where is BNE SKI VESTVEIEN AS based?

BNE SKI VESTVEIEN AS has its business address in Oslo.

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.