biztrac. BETA
COMPANY REGISTER PROFILE
984094493 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Security activities n.e.c.

NALBANT HOLDING AS

Org. no. 984094493 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 417,000
Operating profit NOK 256,000
Equity NOK 25.9m
Incorporated 2002
Share capital NOK 200,000

NALBANT HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 984094493. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Investering innen ulike bransjer, her inkludert it, Telekom, elektro, tjenesteyting og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 417,000 in revenue and NOK 256,000 in operating profit.

Former names: NADCOM AS

Key figures · 2025

Revenue
NOK 417,000
▲ +149 %
Operating profit
NOK 256,000
▲ +308 %
Equity
NOK 25.9m
▼ −21 %
Est. value
NOK 13.9m

Financial health · 2025

Liquidity
39.36
Very good
Current assets ÷ current liabilities
Profitability
12.7%
Good
Return on total assets
Solidity
97.8%
Very good
Equity as a share of total capital

Who owns NALBANT HOLDING AS?

NALBANT HOLDING AS
NOK 417,000 rev. · NOK 256,000 profit

NALBANT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NALBANT HOLDING AS own?

NALBANT HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about NALBANT HOLDING AS

Who owns NALBANT HOLDING AS?

Nadir Nalbant is the largest registered owner, with 100.0%.

What is the revenue of NALBANT HOLDING AS?

NALBANT HOLDING AS had revenue of NOK 417,000 in 2025.

Where is NALBANT HOLDING AS based?

NALBANT 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.