BIZTRAC BETA
COMPANY REGISTER PROFILE
921228880 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

I RECEIPT NORWAY AS

Org. no. 921228880 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −315
Equity NOK −235,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−235k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−315 kr).

I RECEIPT NORWAY AS is registered as a limited company in Oslo, Oslo with organisation number 921228880. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Data og applikasjon programmering og salg.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −315 in operating profit.

Former names: PRESTIGE HOUSE AS

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −315
Equity
NOK −235,000

Financial health · 2024

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

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

Who owns I RECEIPT NORWAY AS?

MOETAZ ISSA
I RECEIPT NORWAY AS
NOK 0 rev. · NOK −315 profit

I RECEIPT NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about I RECEIPT NORWAY AS

Who owns I RECEIPT NORWAY AS?

MOETAZ ISSA is the largest registered owner, with 100.0%.

What is the revenue of I RECEIPT NORWAY AS?

I RECEIPT NORWAY AS had revenue of NOK 0 in 2024.

Where is I RECEIPT NORWAY AS based?

I RECEIPT NORWAY AS has its business address in Oslo.

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.