BIZTRAC BETA
Rental and operating of own or leased real estate

GLASS-SIKRING EIGEDOM AS

Org. no. 981291166 Limited company (AS) Gloppen Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 415,000
Operating profit NOK 302,000
Equity NOK 1.2m
Incorporated 1999
Share capital NOK 30,000

GLASS-SIKRING EIGEDOM AS is registered as a limited company in Gloppen, Vestland with organisation number 981291166. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Kjøp, salg og byggeledelse i forbindelse med oppføring av fast eiendom m.v. samt utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 415,000 in revenue and NOK 302,000 in operating profit.

Key figures · 2025

Revenue
NOK 415,000
Operating profit
NOK 302,000
Equity
NOK 1.2m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns GLASS-SIKRING EIGEDOM AS?

ARILD SÆTHRE
GLASS-SIKRING EIGEDOM AS
NOK 415,000 rev. · NOK 302,000 profit

GLASS-SIKRING EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GLASS-SIKRING EIGEDOM AS

Who owns GLASS-SIKRING EIGEDOM AS?

ARILD SÆTHRE is the largest registered owner, with 50.0%.

What is the revenue of GLASS-SIKRING EIGEDOM AS?

GLASS-SIKRING EIGEDOM AS had revenue of NOK 415,000 in 2025.

Who is the general manager of GLASS-SIKRING EIGEDOM AS?

John Arne Myklebust is registered as general manager of GLASS-SIKRING EIGEDOM AS.

Where is GLASS-SIKRING EIGEDOM AS based?

GLASS-SIKRING EIGEDOM AS has its business address in Sandane.

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.