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

POORTMAN HOLDING AS

Org. no. 928884422 Limited company (AS) Elverum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −188,000
Equity NOK 784,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

POORTMAN HOLDING AS is registered as a limited company in Elverum, Innlandet with organisation number 928884422. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i aksjer og andeler, samt virksomhet som har tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −188,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −188,000
▼ −3120 %
Equity
NOK 784,000
▲ +4124911 %
Est. value
NOK 5.6m

Financial health · 2025

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

Who owns POORTMAN HOLDING AS?

POORTMAN HOLDING AS
NOK 0 rev. · NOK −188,000 profit

POORTMAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POORTMAN HOLDING AS

Who owns POORTMAN HOLDING AS?

IDA MARITA POORTMAN is the largest registered owner, with 100.0%.

What is the revenue of POORTMAN HOLDING AS?

POORTMAN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of POORTMAN HOLDING AS?

Ida Marita Poortman is registered as general manager of POORTMAN HOLDING AS.

Where is POORTMAN HOLDING AS based?

POORTMAN HOLDING AS has its business address in Elverum.

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.