biztrac. BETA
COMPANY REGISTER PROFILE
982980240 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

VESTBY NÆRINGSPARK NORD 1 AS

Org. no. 982980240 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Operating profit NOK −257,000
Equity NOK 2.3m
Incorporated 2001
Share capital NOK 2.3m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−257k kr).

VESTBY NÆRINGSPARK NORD 1 AS is registered as a limited company in Oslo, Oslo with organisation number 982980240. 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 2.3m, divided into 2270 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, herunder drift, utleie og forvaltning av fast eiendom samt hva hermed står i forbindelse. Selskapet kan også delta i andre virksomheter med tilsvarende eller lignende virksomhet.”.

Former names: EAGLE SHARP EIENDOM AS

Key figures · 2025

Operating profit
NOK −257,000
▼ −10 %
Equity
NOK 2.3m
▲ +0 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-1.6%
Not satisfactory
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns VESTBY NÆRINGSPARK NORD 1 AS?

VESTBY NÆRINGSPARK NORD 1 AS
· NOK −257,000 profit

VESTBY NÆRINGSPARK NORD 1 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VESTBY NÆRINGSPARK NORD 1 AS er morselskap for 48 datterselskaper:

Frequently asked questions about VESTBY NÆRINGSPARK NORD 1 AS

Who owns VESTBY NÆRINGSPARK NORD 1 AS?

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

Where is VESTBY NÆRINGSPARK NORD 1 AS based?

VESTBY NÆRINGSPARK NORD 1 AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.