BIZTRAC BETA
Uoppgitt

BLIXRUDI HOLDING AS

Org. no. 925650862 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 50,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

BLIXRUDI HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925650862. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Forestå investeringer i aksjer og andeler i andre selskaper og drive salg av konsulenttjenester samt kunne foreta investeringer i fast eiendom og det som naturlig hører sammen med dette.”.

Key figures · 2024

Operating profit
NOK −18,000
Equity
NOK 50,000
Est. value
NOK 269,000

Financial health · 2024

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

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

Who owns BLIXRUDI HOLDING AS?

INGFRID EMMERENTZE BLIX MORTENSEN
BLIXRUDI HOLDING AS
· NOK −18,000 profit

BLIXRUDI HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BLIXRUDI HOLDING AS own?

BLIXRUDI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BLIXRUDI HOLDING AS

Who owns BLIXRUDI HOLDING AS?

INGFRID EMMERENTZE BLIX MORTENSEN is the largest registered owner, with 50.0%.

Who is the general manager of BLIXRUDI HOLDING AS?

Ingfrid Emmerentze Blix Mortensen is registered as general manager of BLIXRUDI HOLDING AS.

Where is BLIXRUDI HOLDING AS based?

BLIXRUDI HOLDING AS has its business address in Trondheim.

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.