BIZTRAC BETA
Legal activities

GRC AS

Org. no. 922155682 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −81,000
Equity NOK 9.1m
Incorporated 2019
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−81k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRC AS is registered as a limited company in Oslo, Oslo with organisation number 922155682. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Eie, forvalte og utvikle selskap som arbeider med utvikling av digitale løsninger for virksomhetsstyring, herunder løsninger innenfor organisering (governance), risikostyring (risk) og etterlevelse (compliance) av lover, regler og god praksis innen personvern, anti-hvitvasking og beskyttelse mot korrupsjon og andre former for økonomisk kriminalitet og misligheter.”.

Key figures · 2024

Operating profit
NOK −81,000
Equity
NOK 9.1m
Est. value
NOK 36.6m

Financial health · 2025

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

Who owns GRC AS?

ERLING GRIMSTAD
GRC AS
· NOK −81,000 profit

GRC AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRC AS own?

GRC AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about GRC AS

Who owns GRC AS?

ERLING GRIMSTAD is the largest registered owner, with 100.0%.

Who is the general manager of GRC AS?

Erling Grimstad is registered as general manager of GRC AS.

Where is GRC AS based?

GRC 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.