BIZTRAC BETA
Computer consultancy and computer facilities management activities

MEGABITE HOLDING AS

Org. no. 988944327 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 2.6m
Incorporated 2005
Share capital NOK 100,000

Signals

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

MEGABITE HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 988944327. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i verdipapir og eiendom, samt deltagelse i andre virksomheter av enhver art.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 2.6m
Est. value
NOK 25.1m

Financial health · 2025

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

Who owns MEGABITE HOLDING AS?

KJETIL KLEPPE
MEGABITE HOLDING AS
· NOK −16,000 profit

MEGABITE HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MEGABITE HOLDING AS own?

MEGABITE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MEGABITE HOLDING AS

Who owns MEGABITE HOLDING AS?

KJETIL KLEPPE is the largest registered owner, with 50.0%.

Who is the general manager of MEGABITE HOLDING AS?

Øyvind Grødem is registered as general manager of MEGABITE HOLDING AS.

Where is MEGABITE HOLDING AS based?

MEGABITE HOLDING 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.