BIZTRAC BETA
Manufacture of other food products n.e.c.

RIBALDER BRANDS AS

Org. no. 931506617 Limited company (AS) Øyer Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 812,000
Operating profit NOK 303,000
Equity NOK 439,000
Incorporated 2023
Share capital NOK 30,000

RIBALDER BRANDS AS is registered as a limited company in Øyer, Innlandet with organisation number 931506617. The business is classified under manufacture of other food products n.e.c. (NACE 10.890). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Å utvikle, produsere og markedsføre merkevarer, samt annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 812,000 in revenue and NOK 303,000 in operating profit.

Key figures · 2024

Revenue
NOK 812,000
Operating profit
NOK 303,000
Equity
NOK 439,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns RIBALDER BRANDS AS?

KJETIL VEEN
RIBALDER BRANDS AS
NOK 812,000 rev. · NOK 303,000 profit

RIBALDER BRANDS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RIBALDER BRANDS AS own?

RIBALDER BRANDS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RIBALDER BRANDS AS

Who owns RIBALDER BRANDS AS?

KJETIL VEEN is the largest registered owner, with 100.0%.

What is the revenue of RIBALDER BRANDS AS?

RIBALDER BRANDS AS had revenue of NOK 812,000 in 2024.

Who is the general manager of RIBALDER BRANDS AS?

Kjetil Veen is registered as general manager of RIBALDER BRANDS AS.

Where is RIBALDER BRANDS AS based?

RIBALDER BRANDS AS has its business address in Øyer.

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.