BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

FIRA HOLDING AS

Org. no. 934967569 Limited company (AS) Elverum Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 37,000
Incorporated 2025
Share capital NOK 40,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).
  • Nylig endring 2026-07-23 Adresseendring registrert 2026-07-23.

FIRA HOLDING AS is registered as a limited company in Elverum, Innlandet with organisation number 934967569. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2025. Registered share capital is NOK 40,000, divided into 400 shares. The company's stated purpose is: “Investeringsvirksomhet, deltakelse i andre selskaper, finansforvaltning, kjøp, drift, oppføring og rehabilitering av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 37,000
Est. value
NOK 57,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FIRA HOLDING AS?

RAFAL MARCIN FIRA
FIRA HOLDING AS
· NOK −3,000 profit

FIRA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FIRA HOLDING AS own?

FIRA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FIRA HOLDING AS

Who owns FIRA HOLDING AS?

RAFAL MARCIN FIRA is the largest registered owner, with 100.0%.

Who is the general manager of FIRA HOLDING AS?

Rafal Marcin Fira is registered as general manager of FIRA HOLDING AS.

Where is FIRA HOLDING AS based?

FIRA 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 15.06.2026.

Report a problem

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