biztrac. BETA
COMPANY REGISTER PROFILE
831174862 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

IRRI INVEST AS

Org. no. 831174862 Limited company (AS) Gausdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 1.0m
Incorporated 2023
Share capital NOK 30,000

Signals

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

IRRI INVEST AS is registered as a limited company in Gausdal, Innlandet with organisation number 831174862. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom og aksjer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
▼ −9 %
Equity
NOK 1.0m
▲ +0 %
Est. value
NOK 554,000

Financial health · 2025

Liquidity
44.91
Very good
Current assets ÷ current liabilities
Profitability
0.3%
Not satisfactory
Return on total assets
Solidity
97.8%
Very good
Equity as a share of total capital

Who owns IRRI INVEST AS?

SELSKAP IRRI INVEST OY FI
IRRI INVEST AS
NOK 0 rev. · NOK −24,000 profit

IRRI INVEST AS has 1 registered shareholder:

  • SELSKAP IRRI INVEST OY 100.0%
All shareholders and roles →

Frequently asked questions about IRRI INVEST AS

Who owns IRRI INVEST AS?

SELSKAP IRRI INVEST OY is the largest registered owner, with 100.0%.

What is the revenue of IRRI INVEST AS?

IRRI INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of IRRI INVEST AS?

Eino Antero Irri is registered as general manager of IRRI INVEST AS.

Where is IRRI INVEST AS based?

IRRI INVEST AS has its business address in Østre Gausdal.

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

Report a problem

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