BIZTRAC BETA
Computer consultancy and computer facilities management activities

HESBYNETT AS

Org. no. 879924472 Limited company (AS) Stavanger Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 13.9m
Operating profit NOK 489,000
Equity NOK 324,000
Incorporated 1998
Share capital NOK 2.5m

HESBYNETT AS is registered as a limited company in Stavanger, Rogaland with organisation number 879924472. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 1998. Registered share capital is NOK 2.5m, divided into 25000 shares. The company's stated purpose is: “Utvikle en internettbedrift som tilbyr internett samt tilhørende tjenester og utstyr til hele landet. Ved hjelp av datakommunikasjon skal vi bygge opp en internettleverandør/IKT leverandør/konsulentbedrift med samarbeidspartnere spredd ut over hele distriktet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 13.9m in revenue and NOK 489,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.9m
Operating profit
NOK 489,000
Equity
NOK 324,000
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns HESBYNETT AS?

FRODE HESBY
HESBYNETT AS
NOK 13.9m rev. · NOK 489,000 profit

HESBYNETT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HESBYNETT AS

Who owns HESBYNETT AS?

FRODE HESBY is the largest registered owner, with 100.0%.

What is the revenue of HESBYNETT AS?

HESBYNETT AS had revenue of NOK 13.9m in 2024.

Who is the general manager of HESBYNETT AS?

Frode Hesby is registered as general manager of HESBYNETT AS.

Where is HESBYNETT AS based?

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