BIZTRAC BETA
Rental and operating of own or leased real estate

RINGERIKSVEIEN 171 AS

Org. no. 894883022 Limited company (AS) Øvre Eiker Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 824,000
Operating profit NOK 688,000
Equity NOK 595,000
Incorporated 2009
Share capital NOK 54,000

RINGERIKSVEIEN 171 AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 894883022. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 54,000, divided into 155000 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å investere i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 824,000 in revenue and NOK 688,000 in operating profit.

Key figures · 2025

Revenue
NOK 824,000
Operating profit
NOK 688,000
Equity
NOK 595,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.1%
Good
Equity as a share of total capital

Who owns RINGERIKSVEIEN 171 AS?

PISCATORUM HOLDING AS
RINGERIKSVEIEN 171 AS
NOK 824,000 rev. · NOK 688,000 profit

RINGERIKSVEIEN 171 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGERIKSVEIEN 171 AS

Who owns RINGERIKSVEIEN 171 AS?

PISCATORUM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RINGERIKSVEIEN 171 AS?

RINGERIKSVEIEN 171 AS had revenue of NOK 824,000 in 2025.

Who is the general manager of RINGERIKSVEIEN 171 AS?

Carl Axel Sandberg is registered as general manager of RINGERIKSVEIEN 171 AS.

Where is RINGERIKSVEIEN 171 AS based?

RINGERIKSVEIEN 171 AS has its business address in Hokksund.

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.