biztrac. BETA
COMPANY REGISTER PROFILE
981463862 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

BRØDR SÆTH AS

Org. no. 981463862 Limited company (AS) Rauma Incorporated 2000 Active
Revenue 2025 NOK 10.2m
Operating profit NOK 943,000
Equity NOK 3.7m
Incorporated 2000
Employees 6
Share capital NOK 550,000

BRØDR SÆTH AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 981463862. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2000 and has 6 registered employees. Registered share capital is NOK 550,000, divided into 550 shares. The company's stated purpose is: “Rørleggervirksomhet, samt alt hva som naturlig hører under dette, herunder deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.2m in revenue and NOK 943,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.2m
▲ +11 %
Operating profit
NOK 943,000
▲ +67 %
Equity
NOK 3.7m
▲ +25 %
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
3.01
Very good
Current assets ÷ current liabilities
Profitability
19.5%
Very good
Return on total assets
Solidity
68.4%
Very good
Equity as a share of total capital

Who owns BRØDR SÆTH AS?

BRØDR SÆTH AS
NOK 10.2m rev. · NOK 943,000 profit

BRØDR SÆTH AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRØDR SÆTH AS er morselskap for 1 datterselskap:

Frequently asked questions about BRØDR SÆTH AS

Who owns BRØDR SÆTH AS?

GIZMO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRØDR SÆTH AS?

BRØDR SÆTH AS had revenue of NOK 10.2m in 2025.

Who is the general manager of BRØDR SÆTH AS?

Snorre Sæth is registered as general manager of BRØDR SÆTH AS.

Where is BRØDR SÆTH AS based?

BRØDR SÆTH AS has its business address in Åndalsnes.

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

Report a problem

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