BIZTRAC BETA
COMPANY REGISTER PROFILE
926096362 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

PULMENTI HOLDING AS

Org. no. 926096362 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 201,000
Incorporated 2020
Share capital NOK 121,000

Signals

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

PULMENTI HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 926096362. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 121,000, divided into 120500 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −4,000
▼ −34 %
Equity
NOK 201,000
▼ −2 %
Est. value
NOK 237,000

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.9%
Not satisfactory
Return on total assets
Solidity
95.3%
Very good
Equity as a share of total capital

Who owns PULMENTI HOLDING AS?

PULMENTI HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PULMENTI HOLDING AS own?

PULMENTI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PULMENTI HOLDING AS

Who owns PULMENTI HOLDING AS?

DANIEL EDWARD ASHTON NORDÅS is the largest registered owner, with 50.0%.

Who is the general manager of PULMENTI HOLDING AS?

Daniel Edward Ashton Nordås is registered as general manager of PULMENTI HOLDING AS.

Where is PULMENTI HOLDING AS based?

PULMENTI HOLDING AS has its business address in Bærums Verk.

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

Report a problem

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