biztrac. BETA
COMPANY REGISTER PROFILE
922171769 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Growing of vegetables and melons, roots and tubers

UREIST AS

Org. no. 922171769 Limited company (AS) Oslo Incorporated 2019 Active
Revenue 2025 NOK 74.5m
Operating profit NOK −180,000
Equity NOK 9.3m
Incorporated 2019
Employees 47
Share capital NOK 61,000

Signals

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

UREIST AS is registered as a limited company in Oslo, Oslo with organisation number 922171769. The business is classified under growing of vegetables and melons, roots and tubers (NACE 01.130). The company was incorporated in 2019 and has 47 registered employees. Registered share capital is NOK 61,000, divided into 122449 shares. The company's stated purpose is: “Levere dyrking av egenproduserte grønnsaker både ved oppsett og drift av dyrkeplasser.”. The most recent filed accounts, for the 2025 financial year, show NOK 74.5m in revenue and NOK −180,000 in operating profit.

Key figures · 2025

Revenue
NOK 74.5m
▼ −4 %
Operating profit
NOK −180,000
▼ −107 %
Equity
NOK 9.3m
▼ −2 %
Est. value
NOK 6.7m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
-0.5%
Not satisfactory
Return on total assets
Solidity
32.1%
Good
Equity as a share of total capital

Who owns UREIST AS?

UREIST AS
NOK 74.5m rev. · NOK −180,000 profit

UREIST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UREIST AS

Who owns UREIST AS?

FELLESKJØPET AGRI SA is the largest registered owner, with 51.0%.

What is the revenue of UREIST AS?

UREIST AS had revenue of NOK 74.5m in 2025.

Who is the general manager of UREIST AS?

Magnus Humle is registered as general manager of UREIST AS.

Where is UREIST AS based?

UREIST 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 03.10.2026.

Report a problem

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