BIZTRAC BETA
Freezing and further processing of fish, crustaceans and molluscs

KIM RUDI AS

Org. no. 934658779 Limited company (AS) Ål Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK −35,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

KIM RUDI AS is registered as a limited company in Ål, Buskerud with organisation number 934658779. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Slakting og bearbeiding av fisk, røykeri. Salg av fisk og skalldyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK −35,000
Equity
NOK 15,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KIM RUDI AS?

KIM RUDI BJØRNSET BEKKER
KIM RUDI AS
NOK 2.1m rev. · NOK −35,000 profit

KIM RUDI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KIM RUDI AS

Who owns KIM RUDI AS?

KIM RUDI BJØRNSET BEKKER is the largest registered owner, with 100.0%.

What is the revenue of KIM RUDI AS?

KIM RUDI AS had revenue of NOK 2.1m in 2025.

Who is the general manager of KIM RUDI AS?

Kim Rudi Bjørnset Bekker is registered as general manager of KIM RUDI AS.

Where is KIM RUDI AS based?

KIM RUDI AS has its business address in Ål.

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.