BIZTRAC BETA
Raising of animals n.e.c.

KUBE BIRØKT AS

Org. no. 982722586 Limited company (AS) Arendal Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 70,000
Equity NOK 2.2m
Incorporated 2000
Share capital NOK 100,000

KUBE BIRØKT AS is registered as a limited company in Arendal, Agder with organisation number 982722586. The business is classified under raising of animals n.e.c. (NACE 01.489). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Birøkt samt produksjon og salg av varer og tjenester i tilknytning til dette. Selskapet kan også tilby andre typer varer og tjenester, herunder delta i andre selskaper og foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 70,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 70,000
Equity
NOK 2.2m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns KUBE BIRØKT AS?

KURT BIRKELAND
KUBE BIRØKT AS
NOK 3.4m rev. · NOK 70,000 profit

KUBE BIRØKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KUBE BIRØKT AS own?

KUBE BIRØKT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KUBE BIRØKT AS

Who owns KUBE BIRØKT AS?

KURT BIRKELAND is the largest registered owner, with 100.0%.

What is the revenue of KUBE BIRØKT AS?

KUBE BIRØKT AS had revenue of NOK 3.4m in 2025.

Who is the general manager of KUBE BIRØKT AS?

Kurt Birkeland is registered as general manager of KUBE BIRØKT AS.

Where is KUBE BIRØKT AS based?

KUBE BIRØKT AS has its business address in Arendal.

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.