biztrac. BETA
COMPANY REGISTER PROFILE
979488947 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of prepared feeds for farm animals in agriculture

GUNNAR NORDBØ AS

Org. no. 979488947 Limited company (AS) Strand Incorporated 1997 Active
Ownership graph ↗
Operating profit NOK −1.3m
Equity NOK 39.6m
Incorporated 1997
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GUNNAR NORDBØ AS is registered as a limited company in Strand, Rogaland with organisation number 979488947. The business is classified under manufacture of prepared feeds for farm animals in agriculture (NACE 10.911). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 2000 shares. The company's stated purpose is: “Eiendoms- og verdipapirinvestering, samt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −1.3m
▲ +44 %
Equity
NOK 39.6m
▲ +7 %
Est. value
NOK 162.9m

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
29.3%
Very good
Return on total assets
Solidity
59.6%
Very good
Equity as a share of total capital

Who owns GUNNAR NORDBØ AS?

GUNNAR NORDBØ AS has 15 registered shareholders:

All shareholders and roles →

Which companies does GUNNAR NORDBØ AS own?

GUNNAR NORDBØ AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GUNNAR NORDBØ AS

Who owns GUNNAR NORDBØ AS?

Rasmus Nordbø is the largest registered owner, with 10.0%.

Who is the general manager of GUNNAR NORDBØ AS?

Rasmus Nordbø is registered as general manager of GUNNAR NORDBØ AS.

Where is GUNNAR NORDBØ AS based?

GUNNAR NORDBØ AS has its business address in Jørpeland.

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.