BIZTRAC BETA
Retail sale of footwear and leather goods

HØGRI AS

Org. no. 998688205 Limited company (AS) Rakkestad Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 211,000
Equity NOK −420,000
Incorporated 2012
Employees 5
Share capital NOK 400,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−420k kr).

HØGRI AS is registered as a limited company in Rakkestad, Østfold with organisation number 998688205. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 400,000, divided into 1000 shares. The company's stated purpose is: “Detaljhandel med sko og supplerende produkter, samt annen virksomhet og handel som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 211,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 211,000
Equity
NOK −420,000
Est. value
NOK 990,000

Financial health · 2024

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

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

Who owns HØGRI AS?

MAI-IRÉN GRIMSRUD
HØGRI AS
NOK 5.2m rev. · NOK 211,000 profit

HØGRI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HØGRI AS

Who owns HØGRI AS?

MAI-IRÉN GRIMSRUD is the largest registered owner, with 50.0%.

What is the revenue of HØGRI AS?

HØGRI AS had revenue of NOK 5.2m in 2024.

Who is the general manager of HØGRI AS?

Christine Høie Karlsen is registered as general manager of HØGRI AS.

Where is HØGRI AS based?

HØGRI AS has its business address in Rakkestad.

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.