BIZTRAC BETA
Rental and operating of own or leased real estate

SAGVEIEN 17 AS

Org. no. 995324652 Limited company (AS) Indre Østfold Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 1.1m
Equity NOK 5.5m
Incorporated 2010
Share capital NOK 2.9m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SAGVEIEN 17 AS is registered as a limited company in Indre Østfold, Østfold with organisation number 995324652. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 2.9m, divided into 29000 shares. The company's stated purpose is: “Eiendomsvirksomhet samt hva dermed står i forbindelse, herunder deltagelse i andre selskaper, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 1.1m
Equity
NOK 5.5m
Est. value
NOK 5.9m

Financial health · 2024

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

Who owns SAGVEIEN 17 AS?

GLAVA AS
SAGVEIEN 17 AS
NOK 3.8m rev. · NOK 1.1m profit

SAGVEIEN 17 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SAGVEIEN 17 AS er morselskap for 1 datterselskap:

Frequently asked questions about SAGVEIEN 17 AS

Who owns SAGVEIEN 17 AS?

GLAVA AS is the largest registered owner, with 100.0%.

What is the revenue of SAGVEIEN 17 AS?

SAGVEIEN 17 AS had revenue of NOK 3.8m in 2024.

Where is SAGVEIEN 17 AS based?

SAGVEIEN 17 AS has its business address in Askim.

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.