BIZTRAC BETA
Rental and operating of own or leased real estate

BISPEVEIEN 1500 AS

Org. no. 931924990 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 1.9m
Equity NOK 522,000
Incorporated 2023
Share capital NOK 150,000

BISPEVEIEN 1500 AS is registered as a limited company in Tønsberg, Vestfold with organisation number 931924990. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 1.9m
Equity
NOK 522,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns BISPEVEIEN 1500 AS?

HOLMAAS AS
BISPEVEIEN 1500 AS
NOK 2.6m rev. · NOK 1.9m profit

BISPEVEIEN 1500 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BISPEVEIEN 1500 AS

Who owns BISPEVEIEN 1500 AS?

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

What is the revenue of BISPEVEIEN 1500 AS?

BISPEVEIEN 1500 AS had revenue of NOK 2.6m in 2024.

Who is the general manager of BISPEVEIEN 1500 AS?

Anders Aas is registered as general manager of BISPEVEIEN 1500 AS.

Where is BISPEVEIEN 1500 AS based?

BISPEVEIEN 1500 AS has its business address in Våle.

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.