BIZTRAC BETA
COMPANY REGISTER PROFILE
932545012 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Farming of laying hens for production of eggs for consumption

SIREVÅG RUGERI AS

Org. no. 932545012 Limited company (AS) Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 53.0m
Operating profit NOK 17.6m
Equity NOK 21.2m
Incorporated 2023
Employees 10
Share capital NOK 10.0m

SIREVÅG RUGERI AS is registered as a limited company in Hå, Rogaland with organisation number 932545012. The business is classified under farming of laying hens for production of eggs for consumption (NACE 01.471). The company was incorporated in 2023 and has 10 registered employees. Registered share capital is NOK 10.0m, divided into 100000 shares. The company's stated purpose is: “Ruging og klekking av hønekyllinger for eggproduksjon, samt annen virksomhet som naturlig kan knyttes til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 53.0m in revenue and NOK 17.6m in operating profit.

Key figures · 2025

Revenue
NOK 53.0m
Operating profit
NOK 17.6m
▲ +2498 %
Equity
NOK 21.2m
▲ +141 %
Est. value
NOK 38.9m

Financial health · 2025

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
37.6%
Very good
Return on total assets
Solidity
37.9%
Good
Equity as a share of total capital

Who owns SIREVÅG RUGERI AS?

SIREVÅG RUGERI AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIREVÅG RUGERI AS

Who owns SIREVÅG RUGERI AS?

A & A SALTE KYLLINGOPPDRETT AS is the largest registered owner, with 52.0%.

What is the revenue of SIREVÅG RUGERI AS?

SIREVÅG RUGERI AS had revenue of NOK 53.0m in 2025.

Who is the general manager of SIREVÅG RUGERI AS?

Andreas Salte is registered as general manager of SIREVÅG RUGERI AS.

Where is SIREVÅG RUGERI AS based?

SIREVÅG RUGERI AS has its business address in Sirevåg.

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

Report a problem

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