BIZTRAC BETA
Rental and operating of own or leased real estate

BENTSRUDVEIEN 17 AS

Org. no. 991033203 Limited company (AS) Horten Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 1.4m
Equity NOK 2.0m
Incorporated 2007
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.

BENTSRUDVEIEN 17 AS is registered as a limited company in Horten, Vestfold with organisation number 991033203. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendom, løsøre, samt utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 1.4m
Equity
NOK 2.0m
Est. value
NOK 3.5m

Financial health · 2024

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.1%
Satisfactory
Equity as a share of total capital

Who owns BENTSRUDVEIEN 17 AS?

CAPTIVA EIENDOM AS
BENTSRUDVEIEN 17 AS
NOK 1.9m rev. · NOK 1.4m profit

BENTSRUDVEIEN 17 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BENTSRUDVEIEN 17 AS

Who owns BENTSRUDVEIEN 17 AS?

CAPTIVA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BENTSRUDVEIEN 17 AS?

BENTSRUDVEIEN 17 AS had revenue of NOK 1.9m in 2024.

Who is the general manager of BENTSRUDVEIEN 17 AS?

Jon Patrik Mørk is registered as general manager of BENTSRUDVEIEN 17 AS.

Where is BENTSRUDVEIEN 17 AS based?

BENTSRUDVEIEN 17 AS has its business address in Horten.

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.