BIZTRAC BETA
Plumbing installation

STEIN GULSET AS

Org. no. 975963691 Limited company (AS) Bærum Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 11.1m
Operating profit NOK 764,000
Equity NOK 2.0m
Incorporated 1995
Employees 8
Share capital NOK 100,000

STEIN GULSET AS is registered as a limited company in Bærum, Akershus with organisation number 975963691. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1995 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Rørleggerarbeid samt hva hermed står i forbindelse, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.1m in revenue and NOK 764,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.1m
Operating profit
NOK 764,000
Equity
NOK 2.0m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns STEIN GULSET AS?

ØYVIND SCHJØLBERG
STEIN GULSET AS
NOK 11.1m rev. · NOK 764,000 profit

STEIN GULSET AS has 3 registered shareholders:

All shareholders and roles →

Which companies does STEIN GULSET AS own?

STEIN GULSET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEIN GULSET AS

Who owns STEIN GULSET AS?

ØYVIND SCHJØLBERG is the largest registered owner, with 51.0%.

What is the revenue of STEIN GULSET AS?

STEIN GULSET AS had revenue of NOK 11.1m in 2024.

Who is the general manager of STEIN GULSET AS?

Øyvind Schjølberg is registered as general manager of STEIN GULSET AS.

Where is STEIN GULSET AS based?

STEIN GULSET AS has its business address in Blommenholm.

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.