biztrac. BETA
COMPANY REGISTER PROFILE
929646002 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

NYE BA10 HOLDING AS

Org. no. 929646002 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 4.0m
Equity NOK 25.0m
Incorporated 2022
Share capital NOK 1.8m

NYE BA10 HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 929646002. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 1.8m, divided into 1830000 shares. The company's stated purpose is: “Holdingselskap for aksjeinvesteringer og eiendomsselskaper, yte konsulenttjenester og eie og drifte eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 4.0m in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
▲ +10 %
Operating profit
NOK 4.0m
▲ +28 %
Equity
NOK 25.0m
▼ −3 %
Est. value
NOK 23.4m

Financial health · 2025

Liquidity
33.06
Very good
Current assets ÷ current liabilities
Profitability
2.6%
Weak
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns NYE BA10 HOLDING AS?

NYE BA10 HOLDING AS
NOK 4.1m rev. · NOK 4.0m profit

NYE BA10 HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NYE BA10 HOLDING AS own?

NYE BA10 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NYE BA10 HOLDING AS

Who owns NYE BA10 HOLDING AS?

BRM GRUPPEN AS is the largest registered owner, with 50.0%.

What is the revenue of NYE BA10 HOLDING AS?

NYE BA10 HOLDING AS had revenue of NOK 4.1m in 2025.

Where is NYE BA10 HOLDING AS based?

NYE BA10 HOLDING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.