BIZTRAC BETA
Wholesale of other food

BEEFNOR AS

Org. no. 926370715 Limited company (AS) Vindafjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 60.1m
Operating profit NOK 88,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 100,000

BEEFNOR AS is registered as a limited company in Vindafjord, Rogaland with organisation number 926370715. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Innan- og utanlands sal av konsulenttenester innan logistikk og mattrygghet i varestraumen til kjøtt- og annan næringsmiddelindustri. Importera kjøttvarer og trekôl mv. frå Sørlege Afrika og vidaresal til grossist-/detaljhandel internasjonalt.”. The most recent filed accounts, for the 2024 financial year, show NOK 60.1m in revenue and NOK 88,000 in operating profit.

Key figures · 2024

Revenue
NOK 60.1m
Operating profit
NOK 88,000
Equity
NOK 1.1m
Est. value
NOK 970,000

Financial health · 2024

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

Who owns BEEFNOR AS?

BEEFNOR AS
BEEFNOR AS
NOK 60.1m rev. · NOK 88,000 profit

BEEFNOR AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BEEFNOR AS own?

BEEFNOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BEEFNOR AS

Who owns BEEFNOR AS?

BEEFNOR AS is the largest registered owner, with 50.0%.

What is the revenue of BEEFNOR AS?

BEEFNOR AS had revenue of NOK 60.1m in 2024.

Who is the general manager of BEEFNOR AS?

Andriet Van Niekerk is registered as general manager of BEEFNOR AS.

Where is BEEFNOR AS based?

BEEFNOR AS has its business address in Bjoa.

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.