BIZTRAC BETA
Rental and operating of own or leased real estate

JERNBANEVEIEN 1A AS

Org. no. 914329132 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 15.2m
Incorporated 2014
Share capital NOK 30,000

Signals

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

JERNBANEVEIEN 1A AS is registered as a limited company in Oslo, Oslo with organisation number 914329132. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, leie ut og utvikle eiendom og alt annet som naturlig følger av slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 15.2m
Est. value
NOK 13.9m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
86.1%
Very good
Equity as a share of total capital

Who owns JERNBANEVEIEN 1A AS?

CRB HOLDING AS
JERNBANEVEIEN 1A AS
NOK 0 rev. · NOK 0 profit

JERNBANEVEIEN 1A AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JERNBANEVEIEN 1A AS own?

JERNBANEVEIEN 1A AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JERNBANEVEIEN 1A AS

Who owns JERNBANEVEIEN 1A AS?

CRB HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JERNBANEVEIEN 1A AS?

JERNBANEVEIEN 1A AS had revenue of NOK 0 in 2025.

Where is JERNBANEVEIEN 1A AS based?

JERNBANEVEIEN 1A 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.