biztrac. BETA
COMPANY REGISTER PROFILE
823489072 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠OPTIFEED AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other technical consultancy

OPTIFEED AS

Org. no. 823489072 Limited company (AS) Hjelmeland Incorporated 2019 In liquidation
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 53
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

OPTIFEED AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 823489072. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Å drive med konsulenttjenester og FOU prosjekter i oppdrettsnæringen, produksjon og salg av produkter, herunder deltakelse og investering i andre selskap, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −2,000
▲ +77 %
Equity
NOK 53
▼ −98 %

Financial health · 2024

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

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

Who owns OPTIFEED AS?

OPTIFEED AS has 4 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about OPTIFEED AS

Who owns OPTIFEED AS?

Inger Irene Eritzland is the largest registered owner, with 30.0%.

Where is OPTIFEED AS based?

OPTIFEED AS has its business address in Hjelmeland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.