BIZTRAC BETA
Business and other management consultancy activities

BORKA CONSULTING AS

Org. no. 894001682 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −313,000
Equity NOK 244,000
Incorporated 2009
Share capital NOK 100,000

Signals

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

BORKA CONSULTING AS is registered as a limited company in Bærum, Akershus with organisation number 894001682. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bistand innen salg og markedsføring, investering i aksjer og andeler, samt hva hermed følger naturlig med.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −313,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −313,000
Equity
NOK 244,000
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.7%
Good
Equity as a share of total capital

Who owns BORKA CONSULTING AS?

ANDRÉ BORKA
BORKA CONSULTING AS
NOK 2.2m rev. · NOK −313,000 profit

BORKA CONSULTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BORKA CONSULTING AS

Who owns BORKA CONSULTING AS?

ANDRÉ BORKA is the largest registered owner, with 50.0%.

What is the revenue of BORKA CONSULTING AS?

BORKA CONSULTING AS had revenue of NOK 2.2m in 2025.

Who is the general manager of BORKA CONSULTING AS?

André Borka is registered as general manager of BORKA CONSULTING AS.

Where is BORKA CONSULTING AS based?

BORKA CONSULTING AS has its business address in Stabekk.

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.