BIZTRAC BETA
Wholesale of beverages

KANI CONSULTING AS

Org. no. 980624544 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 37,000
Operating profit NOK 16,000
Equity NOK 1.1m
Incorporated 1999
Share capital NOK 400,000

KANI CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 980624544. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 1999. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Selskapets virksomhet er import og engroshandel av alkoholholdige drikkevarer, rådgivningsvirksomhet og annen virksomhet med økonomisk formål”. The most recent filed accounts, for the 2025 financial year, show NOK 37,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 37,000
Operating profit
NOK 16,000
Equity
NOK 1.1m
Est. value
NOK 573,000

Financial health · 2024

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

Who owns KANI CONSULTING AS?

ÅGE LARSEN
KANI CONSULTING AS
NOK 37,000 rev. · NOK 16,000 profit

KANI CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KANI CONSULTING AS own?

KANI CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KANI CONSULTING AS

Who owns KANI CONSULTING AS?

ÅGE LARSEN is the largest registered owner, with 100.0%.

What is the revenue of KANI CONSULTING AS?

KANI CONSULTING AS had revenue of NOK 37,000 in 2025.

Who is the general manager of KANI CONSULTING AS?

Åge Larsen is registered as general manager of KANI CONSULTING AS.

Where is KANI CONSULTING AS based?

KANI CONSULTING AS has its business address in Oslo.

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.