BIZTRAC BETA
Operation of freshwater fish farms

REKEVIG ØRRET AS

Org. no. 926412922 Limited company (AS) Flekkefjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 585,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 1.0m

REKEVIG ØRRET AS is registered as a limited company in Flekkefjord, Agder with organisation number 926412922. The business is classified under operation of freshwater fish farms (NACE 03.221). The company was incorporated in 2020. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Drive produksjon og salg av fisk og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre ser interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 585,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 585,000
Equity
NOK 1.2m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
5.33
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns REKEVIG ØRRET AS?

VIDAR BIRKELAND
REKEVIG ØRRET AS
NOK 3.7m rev. · NOK 585,000 profit

REKEVIG ØRRET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REKEVIG ØRRET AS

Who owns REKEVIG ØRRET AS?

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

What is the revenue of REKEVIG ØRRET AS?

REKEVIG ØRRET AS had revenue of NOK 3.7m in 2024.

Who is the general manager of REKEVIG ØRRET AS?

Vidar Birkeland is registered as general manager of REKEVIG ØRRET AS.

Where is REKEVIG ØRRET AS based?

REKEVIG ØRRET AS has its business address in Sira.

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.