BIZTRAC BETA
Rental and operating of own or leased real estate

SAGELL HOLDING AS

Org. no. 993568929 Limited company (AS) Bømlo Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 286,000
Equity NOK 1.3m
Incorporated 2008
Share capital NOK 450,000

SAGELL HOLDING AS is registered as a limited company in Bømlo, Vestland with organisation number 993568929. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 450,000, divided into 100 shares. The company's stated purpose is: “Utleie av eiendom til næringsdrivende, utleie av arbeidskraft samt kjøp og salg av kjøretøy. I tillegg investering i fast eiendom og verdipapirer hvor det vurderes som interessant for selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 286,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 286,000
Equity
NOK 1.3m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns SAGELL HOLDING AS?

STÅLE SAGVAAG
SAGELL HOLDING AS
NOK 1.6m rev. · NOK 286,000 profit

SAGELL HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAGELL HOLDING AS

Who owns SAGELL HOLDING AS?

STÅLE SAGVAAG is the largest registered owner, with 50.0%.

What is the revenue of SAGELL HOLDING AS?

SAGELL HOLDING AS had revenue of NOK 1.6m in 2025.

Who is the general manager of SAGELL HOLDING AS?

Ståle Sagvaag is registered as general manager of SAGELL HOLDING AS.

Where is SAGELL HOLDING AS based?

SAGELL HOLDING AS has its business address in Rubbestadneset.

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.