BIZTRAC BETA
COMPANY REGISTER PROFILE
936645313 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

HØGRIKA AS

Org. no. 936645313 Limited company (AS) Rakkestad Incorporated 2025 Active
Ownership graph ↗
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-25.

HØGRIKA AS is registered as a limited company in Rakkestad, Østfold with organisation number 936645313. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å investere i eiendom, samt i andre selskaper, herunder kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Equity
NOK 24,000
Est. value
NOK 16,000

Financial health · 2025

Liquidity
4.62
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
78.3%
Weak
Equity as a share of total capital

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

Who owns HØGRIKA AS?

HØGRIKA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HØGRIKA AS

Who owns HØGRIKA AS?

BJØRN SIMEN GRIMSRUD is the largest registered owner, with 33.3%.

Where is HØGRIKA AS based?

HØGRIKA AS has its business address in Rakkestad.

Property

Business address Herrefosserveien 231, 1894 Rakkestad
Cadastral unit 3120-52/1/0/0
Building Enebolig · 2 units

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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