BIZTRAC BETA
Auditing

FGH AUDIT AS

Org. no. 818712642 Limited company (AS) Sandefjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 544,000
Equity NOK 30,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FGH AUDIT AS is registered as a limited company in Sandefjord, Vestfold with organisation number 818712642. The business is classified under auditing (NACE 69.201). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Revisjonsvirksomhet, samt naturlig tilknyttet konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 544,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 544,000
Equity
NOK 30,000
Est. value
NOK 1.8m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FGH AUDIT AS?

FGH HOLDING AS
FGH AUDIT AS
NOK 1.7m rev. · NOK 544,000 profit

FGH AUDIT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FGH AUDIT AS er morselskap for 4 datterselskaper:

Frequently asked questions about FGH AUDIT AS

Who owns FGH AUDIT AS?

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

What is the revenue of FGH AUDIT AS?

FGH AUDIT AS had revenue of NOK 1.7m in 2024.

Who is the general manager of FGH AUDIT AS?

Kay Vidar Thomassen is registered as general manager of FGH AUDIT AS.

Where is FGH AUDIT AS based?

FGH AUDIT AS has its business address in Sandefjord.

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.