BIZTRAC BETA
Development of building projects

AGIL YIELD AS

Org. no. 917986150 Limited company (AS) Larvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2023 NOK 120,000
Operating profit NOK −1.2m
Equity NOK −1.5m
Incorporated 2016
Share capital NOK 2.6m

Signals

3 flags
  • Negativ egenkapital 2023 Bokført egenkapital er negativ (−1,5 mill kr).
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−1,2 mill kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

AGIL YIELD AS is registered as a limited company in Larvik, Vestfold with organisation number 917986150. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 2.6m, divided into 2600 shares. The company's stated purpose is: “Rådgivning, utvikling, kjøp, salg og/eller utleie av eiendom og annen investeringsvirksomhet og verdipapirhandel, utvikling av forretningsideer, samt annen økonomisk virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2023 financial year, show NOK 120,000 in revenue and NOK −1.2m in operating profit.

Key figures · 2023

Revenue
NOK 120,000
Operating profit
NOK −1.2m
Equity
NOK −1.5m

Financial health · 2024

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

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

Who owns AGIL YIELD AS?

No shareholders are registered for AGIL YIELD AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about AGIL YIELD AS

What is the revenue of AGIL YIELD AS?

AGIL YIELD AS had revenue of NOK 120,000 in 2023.

Where is AGIL YIELD AS based?

AGIL YIELD AS has its business address in Larvik.

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.