BIZTRAC BETA
COMPANY REGISTER PROFILE
998235677 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other technical consultancy

GO SPRINKLER AS

Org. no. 998235677 Limited company (AS) Hamar Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 639,000
Equity NOK 786,000
Incorporated 2012
Share capital NOK 30,000

GO SPRINKLER AS is registered as a limited company in Hamar, Innlandet with organisation number 998235677. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets formål er utredning, prosjektering, kontroll og utførelse av sprinkleranlegg og andre typer vannbaserte slokkeanlegg, og handel som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 639,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +5 %
Operating profit
NOK 639,000
▲ +10 %
Equity
NOK 786,000
▲ +24 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
1.98
Good
Current assets ÷ current liabilities
Profitability
38.3%
Very good
Return on total assets
Solidity
49.5%
Very good
Equity as a share of total capital

Who owns GO SPRINKLER AS?

GO SPRINKLER AS
NOK 1.9m rev. · NOK 639,000 profit

GO SPRINKLER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GO SPRINKLER AS

Who owns GO SPRINKLER AS?

GRO FJERDUMSMOEN is the largest registered owner, with 100.0%.

What is the revenue of GO SPRINKLER AS?

GO SPRINKLER AS had revenue of NOK 1.9m in 2025.

Who is the general manager of GO SPRINKLER AS?

Gro Fjerdumsmoen is registered as general manager of GO SPRINKLER AS.

Where is GO SPRINKLER AS based?

GO SPRINKLER AS has its business address in Hamar.

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

Report a problem

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