BIZTRAC BETA
Rental and operating of own or leased real estate

ORSTADVEIEN 108 KLEPP AS

Org. no. 996193187 Limited company (AS) Sandnes Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 3.0m
Equity NOK 1.4m
Incorporated 2010
Share capital NOK 100,000

Signals

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

ORSTADVEIEN 108 KLEPP AS is registered as a limited company in Sandnes, Rogaland with organisation number 996193187. 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 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg, herunder utleie og drift av fast eiendom, samt å delta i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 3.0m
Equity
NOK 1.4m
Est. value
NOK 4.9m

Financial health · 2024

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.6%
Weak
Equity as a share of total capital

Who owns ORSTADVEIEN 108 KLEPP AS?

ORSTADVEIEN 110 AS
ORSTADVEIEN 108 KLEPP AS
NOK 4.6m rev. · NOK 3.0m profit

ORSTADVEIEN 108 KLEPP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORSTADVEIEN 108 KLEPP AS

Who owns ORSTADVEIEN 108 KLEPP AS?

ORSTADVEIEN 110 AS is the largest registered owner, with 100.0%.

What is the revenue of ORSTADVEIEN 108 KLEPP AS?

ORSTADVEIEN 108 KLEPP AS had revenue of NOK 4.6m in 2024.

Where is ORSTADVEIEN 108 KLEPP AS based?

ORSTADVEIEN 108 KLEPP AS has its business address in Sandnes.

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.