BIZTRAC BETA
Rental and operating of own or leased real estate

ELDØYANE 191 AS

Org. no. 823351372 Limited company (AS) Stord Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 2.1m
Equity NOK −1.3m
Incorporated 2019
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ELDØYANE 191 AS is registered as a limited company in Stord, Vestland with organisation number 823351372. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 19970 shares. The company's stated purpose is: “Eie fast eiendom og virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 2.1m
Equity
NOK −1.3m
Est. value
NOK 14.3m

Financial health · 2024

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

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

Who owns ELDØYANE 191 AS?

GREENMOUNTAIN BIOCO, S.L.
ELDØYANE 191 AS
NOK 3.7m rev. · NOK 2.1m profit

ELDØYANE 191 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELDØYANE 191 AS

Who owns ELDØYANE 191 AS?

GREENMOUNTAIN BIOCO, S.L. is the largest registered owner, with 100.0%.

What is the revenue of ELDØYANE 191 AS?

ELDØYANE 191 AS had revenue of NOK 3.7m in 2024.

Where is ELDØYANE 191 AS based?

ELDØYANE 191 AS has its business address in Stord.

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.