BIZTRAC BETA
Construction of residential and non-residential buildings

AGNEFESTVEIEN AS

Org. no. 993068152 Limited company (AS) Lyngdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 79,000
Operating profit NOK 32,000
Equity NOK −2.6m
Incorporated 2008
Share capital NOK 600,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,6 mill kr).

AGNEFESTVEIEN AS is registered as a limited company in Lyngdal, Agder with organisation number 993068152. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Kjøpe, selge, leie ut og utvikle eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 79,000 in revenue and NOK 32,000 in operating profit.

Key figures · 2024

Revenue
NOK 79,000
Operating profit
NOK 32,000
Equity
NOK −2.6m
Est. value
NOK 158,000

Financial health · 2024

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

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

Who owns AGNEFESTVEIEN AS?

SVEIN BIRKELAND
AGNEFESTVEIEN AS
NOK 79,000 rev. · NOK 32,000 profit

AGNEFESTVEIEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGNEFESTVEIEN AS

Who owns AGNEFESTVEIEN AS?

SVEIN BIRKELAND is the largest registered owner, with 100.0%.

What is the revenue of AGNEFESTVEIEN AS?

AGNEFESTVEIEN AS had revenue of NOK 79,000 in 2024.

Who is the general manager of AGNEFESTVEIEN AS?

Svein Birkeland is registered as general manager of AGNEFESTVEIEN AS.

Where is AGNEFESTVEIEN AS based?

AGNEFESTVEIEN AS has its business address in Lyngdal.

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.