BIZTRAC BETA
Buying and selling of own real estate

BANEBAKKEN 38 AS

Org. no. 916335423 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −726,000
Equity NOK 51.6m
Incorporated 2015
Share capital NOK 139,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−726k kr).

BANEBAKKEN 38 AS is registered as a limited company in Oslo, Oslo with organisation number 916335423. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 139,000, divided into 138810 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −726,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −726,000
Equity
NOK 51.6m
Est. value
NOK 83.5m

Financial health · 2024

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

Who owns BANEBAKKEN 38 AS?

STIFTELSEN SCHEIBLER
BANEBAKKEN 38 AS
NOK 0 rev. · NOK −726,000 profit

BANEBAKKEN 38 AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does BANEBAKKEN 38 AS own?

BANEBAKKEN 38 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BANEBAKKEN 38 AS

Who owns BANEBAKKEN 38 AS?

STIFTELSEN SCHEIBLER is the largest registered owner, with 37.7%.

What is the revenue of BANEBAKKEN 38 AS?

BANEBAKKEN 38 AS had revenue of NOK 0 in 2024.

Where is BANEBAKKEN 38 AS based?

BANEBAKKEN 38 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.