BIZTRAC BETA
Rental and operating of own or leased real estate

BORTELIDSETER NÆRINGSPARK AS

Org. no. 983820204 Limited company (AS) Åseral Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −62,000
Equity NOK 2.8m
Incorporated 2002
Share capital NOK 105,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BORTELIDSETER NÆRINGSPARK AS is registered as a limited company in Åseral, Agder with organisation number 983820204. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 105,000, divided into 240 shares. The company's stated purpose is: “Utvikling og salg av tomter og fritidsleiligheter, hotelldrift og utleie av leiligheter, samt alt hva hermed står i forbindelse, herunder å delta i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −62,000
Equity
NOK 2.8m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns BORTELIDSETER NÆRINGSPARK AS?

GOD DRIV AS
BORTELIDSETER NÆRINGSPARK AS
· NOK −62,000 profit

BORTELIDSETER NÆRINGSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORTELIDSETER NÆRINGSPARK AS

Who owns BORTELIDSETER NÆRINGSPARK AS?

GOD DRIV AS is the largest registered owner, with 100.0%.

Who is the general manager of BORTELIDSETER NÆRINGSPARK AS?

Torkjell Tofte is registered as general manager of BORTELIDSETER NÆRINGSPARK AS.

Where is BORTELIDSETER NÆRINGSPARK AS based?

BORTELIDSETER NÆRINGSPARK AS has its business address in Åseral.

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.