biztrac. BETA
COMPANY REGISTER PROFILE
918744967 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

FRETTEM HOLDING AS

Org. no. 918744967 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −83,000
Incorporated 2017
Share capital NOK 60,000

Signals

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

FRETTEM HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 918744967. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet, informasjonsteknologi, deltakelse i andre selskaper, generell investeringsvirksomhet, herunder handel med verdipapirer, investering i selskaper, eiendom og andre aktiva.”.

Former names: BRUKTMEGLEREN AS

Key figures · 2025

Operating profit
NOK −83,000
▼ −191 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

Who owns FRETTEM HOLDING AS?

FRETTEM HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FRETTEM HOLDING AS own?

FRETTEM HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FRETTEM HOLDING AS

Who owns FRETTEM HOLDING AS?

Henning Kvammen Frettem is the largest registered owner, with 50.0%.

Who is the general manager of FRETTEM HOLDING AS?

Henning Kvammen Frettem is registered as general manager of FRETTEM HOLDING AS.

Where is FRETTEM HOLDING AS based?

FRETTEM HOLDING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.