BIZTRAC BETA
Electrical installation

GO SERVICE AS

Org. no. 925797839 Limited company (AS) Hol Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −68,000
Equity NOK 0
Incorporated 2020
Share capital NOK 30,000

Signals

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

GO SERVICE AS is registered as a limited company in Hol, Buskerud with organisation number 925797839. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenester innen elektro og elektroingeniør, samt relaterte tjenester, herunder utleie on-shore og off-shore i Norge og i utlandet. I tillegg skal selskapet investere i andre selskap i tilstøtende bransjer, samt eiendom og andre relevante investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −68,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −68,000
Equity
NOK 0

Financial health · 2024

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

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

Who owns GO SERVICE AS?

BJØRN VIK
GO SERVICE AS
NOK 0 rev. · NOK −68,000 profit

GO SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GO SERVICE AS

Who owns GO SERVICE AS?

BJØRN VIK is the largest registered owner, with 100.0%.

What is the revenue of GO SERVICE AS?

GO SERVICE AS had revenue of NOK 0 in 2024.

Who is the general manager of GO SERVICE AS?

Bjørn Vik is registered as general manager of GO SERVICE AS.

Where is GO SERVICE AS based?

GO SERVICE AS has its business address in Hol.

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.