BIZTRAC BETA
Other technical consultancy

GASS OG PUSTESERVICE AS

Org. no. 890191282 Limited company (AS) Frogn Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 21.9m
Operating profit NOK 2.4m
Equity NOK 2.5m
Incorporated 2006
Employees 8
Share capital NOK 100,000

GASS OG PUSTESERVICE AS is registered as a limited company in Frogn, Akershus with organisation number 890191282. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2006 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Service og annet arbeide tilknyttet pustevernsutstyr, teknologi og gass. Engroshandel, opplæring og annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.9m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 21.9m
Operating profit
NOK 2.4m
Equity
NOK 2.5m
Est. value
NOK 12.3m

Financial health · 2024

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

Who owns GASS OG PUSTESERVICE AS?

MICHAEL SIGMUND HANSSON
GASS OG PUSTESERVICE AS
NOK 21.9m rev. · NOK 2.4m profit

GASS OG PUSTESERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GASS OG PUSTESERVICE AS

Who owns GASS OG PUSTESERVICE AS?

MICHAEL SIGMUND HANSSON is the largest registered owner, with 40.9%.

What is the revenue of GASS OG PUSTESERVICE AS?

GASS OG PUSTESERVICE AS had revenue of NOK 21.9m in 2024.

Who is the general manager of GASS OG PUSTESERVICE AS?

Øyvind Martin Wiig Knutsen is registered as general manager of GASS OG PUSTESERVICE AS.

Where is GASS OG PUSTESERVICE AS based?

GASS OG PUSTESERVICE AS has its business address in Drøbak.

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.