BIZTRAC BETA
Computer consultancy and computer facilities management activities

FHIRD AS

Org. no. 994587110 Limited company (AS) Fredrikstad Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK −240,000
Equity NOK 392,000
Incorporated 2009
Share capital NOK 100,000

Signals

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

FHIRD AS is registered as a limited company in Fredrikstad, Østfold with organisation number 994587110. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Konsulenttjenester innen fintech og annen informasjonsteknologi, samt drift og utvikling av egne og andre selskapers digitale løsninger. Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK −240,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK −240,000
Equity
NOK 392,000
Est. value
NOK 6.3m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.7%
Good
Equity as a share of total capital

Who owns FHIRD AS?

NEXT GROUP HOLDING AS
FHIRD AS
NOK 3.6m rev. · NOK −240,000 profit

FHIRD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FHIRD AS

Who owns FHIRD AS?

NEXT GROUP HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FHIRD AS?

FHIRD AS had revenue of NOK 3.6m in 2024.

Where is FHIRD AS based?

FHIRD AS has its business address in Gamle Fredrikstad.

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.