biztrac. BETA
COMPANY REGISTER PROFILE
991372482 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Farming of laying hens for production of eggs for consumption

STULEN FJØRFE AS

Org. no. 991372482 Limited company (AS) Sandefjord Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 7.6m
Operating profit NOK 1.5m
Equity NOK 5.2m
Incorporated 2007
Share capital NOK 100,000

STULEN FJØRFE AS is registered as a limited company in Sandefjord, Vestfold with organisation number 991372482. The business is classified under farming of laying hens for production of eggs for consumption (NACE 01.471). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produksjon av fjørfekjøtt, herunder deltakelse i andre selskaper og hva som derved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.6m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 7.6m
▲ +11 %
Operating profit
NOK 1.5m
▲ +23 %
Equity
NOK 5.2m
▲ +18 %
Est. value
NOK 5.9m

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
11.2%
Good
Return on total assets
Solidity
40.8%
Very good
Equity as a share of total capital

Who owns STULEN FJØRFE AS?

STULEN FJØRFE AS
NOK 7.6m rev. · NOK 1.5m profit

STULEN FJØRFE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STULEN FJØRFE AS

Who owns STULEN FJØRFE AS?

Harald Øyvind Rød is the largest registered owner, with 100.0%.

What is the revenue of STULEN FJØRFE AS?

STULEN FJØRFE AS had revenue of NOK 7.6m in 2025.

Who is the general manager of STULEN FJØRFE AS?

Harald Øyvind Rød is registered as general manager of STULEN FJØRFE AS.

Where is STULEN FJØRFE AS based?

STULEN FJØRFE AS has its business address in Andebu.

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.