BIZTRAC BETA
Plumbing installation

BIRI RØRSERVICE AS

Org. no. 931819011 Limited company (AS) Gjøvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 13.2m
Operating profit NOK 392,000
Equity NOK 784,000
Incorporated 2023
Employees 6
Share capital NOK 250,000

BIRI RØRSERVICE AS is registered as a limited company in Gjøvik, Innlandet with organisation number 931819011. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 250,000, divided into 250000 shares. The company's stated purpose is: “Salg av varer og tjenester innenfor VVS (vann, varme og sanitær) og andre forretningsområder som er naturlig i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.2m in revenue and NOK 392,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.2m
Operating profit
NOK 392,000
Equity
NOK 784,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns BIRI RØRSERVICE AS?

VISMUND GRUPPEN AS
BIRI RØRSERVICE AS
NOK 13.2m rev. · NOK 392,000 profit

BIRI RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BIRI RØRSERVICE AS er morselskap for 3 datterselskaper:

Frequently asked questions about BIRI RØRSERVICE AS

Who owns BIRI RØRSERVICE AS?

VISMUND GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of BIRI RØRSERVICE AS?

BIRI RØRSERVICE AS had revenue of NOK 13.2m in 2024.

Who is the general manager of BIRI RØRSERVICE AS?

Jon Arne Schjetne is registered as general manager of BIRI RØRSERVICE AS.

Where is BIRI RØRSERVICE AS based?

BIRI RØRSERVICE AS has its business address in Biri.

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.