BIZTRAC BETA
COMPANY REGISTER PROFILE
926425145 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

ERLEND STEGAVIK RYGG HOLDING AS

Org. no. 926425145 Limited company (AS) Hol Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 148,000
Incorporated 2021
Share capital NOK 40,000

Signals

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

ERLEND STEGAVIK RYGG HOLDING AS is registered as a limited company in Hol, Buskerud with organisation number 926425145. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Investere i andre virksomheter gjennom aksjer eller på annen måte, samt salg av konsulenttjenester og virksomhet som naturlig faller inn under dette.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK 148,000
Est. value
NOK 343,000

Financial health · 2024

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

Who owns ERLEND STEGAVIK RYGG HOLDING AS?

ERLEND STEGAVIK RYGG
ERLEND STEGAVIK RYGG HOLDING AS
· NOK −3,000 profit

ERLEND STEGAVIK RYGG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERLEND STEGAVIK RYGG HOLDING AS

Who owns ERLEND STEGAVIK RYGG HOLDING AS?

ERLEND STEGAVIK RYGG is the largest registered owner, with 100.0%.

Who is the general manager of ERLEND STEGAVIK RYGG HOLDING AS?

Erlend Stegavik Rygg is registered as general manager of ERLEND STEGAVIK RYGG HOLDING AS.

Where is ERLEND STEGAVIK RYGG HOLDING AS based?

ERLEND STEGAVIK RYGG HOLDING AS has its business address in Geilo.

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.