BIZTRAC BETA
Plumbing installation

GASS OG RØRSERVICE AS

Org. no. 914828953 Limited company (AS) Porsgrunn Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 241,000
Equity NOK 2.4m
Incorporated 2015
Share capital NOK 30,000

GASS OG RØRSERVICE AS is registered as a limited company in Porsgrunn, Telemark with organisation number 914828953. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Rørlegging, installasjon og service innen gass og vann.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 241,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
Operating profit
NOK 241,000
Equity
NOK 2.4m
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
2.94
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.8%
Very good
Equity as a share of total capital

Who owns GASS OG RØRSERVICE AS?

THOMAS SOLLI BRÅTEN
GASS OG RØRSERVICE AS
NOK 6.0m rev. · NOK 241,000 profit

GASS OG RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GASS OG RØRSERVICE AS own?

GASS OG RØRSERVICE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GASS OG RØRSERVICE AS

Who owns GASS OG RØRSERVICE AS?

THOMAS SOLLI BRÅTEN is the largest registered owner, with 100.0%.

What is the revenue of GASS OG RØRSERVICE AS?

GASS OG RØRSERVICE AS had revenue of NOK 6.0m in 2025.

Who is the general manager of GASS OG RØRSERVICE AS?

Thomas Solli Bråten is registered as general manager of GASS OG RØRSERVICE AS.

Where is GASS OG RØRSERVICE AS based?

GASS OG RØRSERVICE AS has its business address in Porsgrunn.

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.