BIZTRAC BETA
Business and other management consultancy activities

OE KANESTRØM CONSULTING AS

Org. no. 920061923 Limited company (AS) Vestby Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 69,000
Operating profit NOK −19,000
Equity NOK 336,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

OE KANESTRØM CONSULTING AS is registered as a limited company in Vestby, Akershus with organisation number 920061923. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Yte økonomisk og administrativ konsulentbistand, samt kjøp og salg av aksjer og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 69,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 69,000
Operating profit
NOK −19,000
Equity
NOK 336,000
Est. value
NOK 202,000

Financial health · 2025

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

Who owns OE KANESTRØM CONSULTING AS?

ODD EGIL KANESTRØM
OE KANESTRØM CONSULTING AS
NOK 69,000 rev. · NOK −19,000 profit

OE KANESTRØM CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OE KANESTRØM CONSULTING AS

Who owns OE KANESTRØM CONSULTING AS?

ODD EGIL KANESTRØM is the largest registered owner, with 100.0%.

What is the revenue of OE KANESTRØM CONSULTING AS?

OE KANESTRØM CONSULTING AS had revenue of NOK 69,000 in 2025.

Where is OE KANESTRØM CONSULTING AS based?

OE KANESTRØM CONSULTING AS has its business address in Son.

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.