BIZTRAC BETA
Sports activities n.e.c.

BYBERG CONSULTING AS

Org. no. 914330203 Limited company (AS) Stavanger Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −53,000
Equity NOK 7.8m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−53k kr).

BYBERG CONSULTING AS is registered as a limited company in Stavanger, Rogaland with organisation number 914330203. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Konsulentvirksomhet innen idrettsarrangement, finansielle tjenester og andre produkter/tjenester som naturlig hører sammen med dette. Herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −53,000
Equity
NOK 7.8m
Est. value
NOK 38.9m

Financial health · 2025

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

Who owns BYBERG CONSULTING AS?

SVEINUNG BYBERG
BYBERG CONSULTING AS
· NOK −53,000 profit

BYBERG CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BYBERG CONSULTING AS own?

BYBERG CONSULTING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BYBERG CONSULTING AS

Who owns BYBERG CONSULTING AS?

SVEINUNG BYBERG is the largest registered owner, with 100.0%.

Who is the general manager of BYBERG CONSULTING AS?

Sveinung Byberg is registered as general manager of BYBERG CONSULTING AS.

Where is BYBERG CONSULTING AS based?

BYBERG CONSULTING 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.