BIZTRAC BETA
COMPANY REGISTER PROFILE
925777870 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SELIAM HOLDING AS

Org. no. 925777870 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

SELIAM HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 925777870. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forvaltning av eierinteresser, inklusive eiendom, og det som måtte stå i den forbindelse.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −29 %
Equity
NOK 1.6m
▲ +11 %
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns SELIAM HOLDING AS?

SELIAM HOLDING AS
· NOK −8,000 profit

SELIAM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SELIAM HOLDING AS

Who owns SELIAM HOLDING AS?

JAN KVAMME IQBAL is the largest registered owner, with 100.0%.

Where is SELIAM HOLDING AS based?

SELIAM HOLDING AS has its business address in Jar.

Property

Business address c/o Jan Kvamme Iqbal Vollsveien 111A, 1358 Jar
Cadastral unit 3201-36/149/0/0
Building Tomannsbolig, vertikal · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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