BIZTRAC BETA
Geological surveying

SKRID AKTSOMHET AS

Org. no. 926642111 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK −195,000
Equity NOK 210,000
Incorporated 2021
Employees 9
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−195k kr).

SKRID AKTSOMHET AS is registered as a limited company in Stavanger, Rogaland with organisation number 926642111. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2021 and has 9 registered employees. Registered share capital is NOK 60,000, divided into 80000 shares. The company's stated purpose is: “Tilby service og tjenester innen geologiske vurderinger. Selskapet kan også ha eierskap i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK −195,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK −195,000
Equity
NOK 210,000
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns SKRID AKTSOMHET AS?

SKRID HOLDING AS
SKRID AKTSOMHET AS
NOK 5.6m rev. · NOK −195,000 profit

SKRID AKTSOMHET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKRID AKTSOMHET AS

Who owns SKRID AKTSOMHET AS?

SKRID HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SKRID AKTSOMHET AS?

SKRID AKTSOMHET AS had revenue of NOK 5.6m in 2024.

Who is the general manager of SKRID AKTSOMHET AS?

Rasmus Sødal Pedersen is registered as general manager of SKRID AKTSOMHET AS.

Where is SKRID AKTSOMHET AS based?

SKRID AKTSOMHET AS has its business address in Stavanger.

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.