BIZTRAC BETA
Development of building projects

AGDERBYEN 8 AS

Org. no. 996270246 Limited company (AS) Lillesand Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK −19,000
Incorporated 2010
Share capital NOK 151,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−19k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AGDERBYEN 8 AS is registered as a limited company in Lillesand, Agder with organisation number 996270246. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2010. Registered share capital is NOK 151,000, divided into 150694 shares. The company's stated purpose is: “Eiendomsutvikling og tomtesalg, samt hva herved står i forbindelse, herunder deltakelse i annen virksomhet ved aksjeeie eller på annen måte.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK −19,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AGDERBYEN 8 AS?

SKIFJELL INVEST AS
AGDERBYEN 8 AS
· NOK −12,000 profit

AGDERBYEN 8 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AGDERBYEN 8 AS er morselskap for 28 datterselskaper:

Frequently asked questions about AGDERBYEN 8 AS

Who owns AGDERBYEN 8 AS?

SKIFJELL INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of AGDERBYEN 8 AS?

Kurt Palm is registered as general manager of AGDERBYEN 8 AS.

Where is AGDERBYEN 8 AS based?

AGDERBYEN 8 AS has its business address in Lillesand.

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.