BIZTRAC BETA
Rental and operating of own or leased real estate

LUREVEIEN 66 AS

Org. no. 984105835 Limited company (AS) Bergen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 247,000
Equity NOK 3.3m
Incorporated 2001
Share capital NOK 200,000

Signals

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

LUREVEIEN 66 AS is registered as a limited company in Bergen, Vestland with organisation number 984105835. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 247,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 247,000
Equity
NOK 3.3m
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns LUREVEIEN 66 AS?

HØLLELAND EIENDOM AS
LUREVEIEN 66 AS
NOK 1.5m rev. · NOK 247,000 profit

LUREVEIEN 66 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUREVEIEN 66 AS

Who owns LUREVEIEN 66 AS?

HØLLELAND EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of LUREVEIEN 66 AS?

LUREVEIEN 66 AS had revenue of NOK 1.5m in 2025.

Where is LUREVEIEN 66 AS based?

LUREVEIEN 66 AS has its business address in Bergen.

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.