biztrac. BETA
COMPANY REGISTER PROFILE
931793322 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

BORCH CONSULTING AS

Org. no. 931793322 Limited company (AS) Jevnaker Incorporated 2023 Active
Revenue 2025 NOK 314,000
Operating profit NOK 310,000
Equity NOK 269,000
Incorporated 2023
Share capital NOK 30,000

BORCH CONSULTING AS is registered as a limited company in Jevnaker, Akershus with organisation number 931793322. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Bedriftsrådgivning og annen administrativ rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 314,000 in revenue and NOK 310,000 in operating profit.

Key figures · 2025

Revenue
NOK 314,000
Operating profit
NOK 310,000
▲ +1546 %
Equity
NOK 269,000
▲ +10231 %
Est. value
NOK 650,000

Financial health · 2025

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

Who owns BORCH CONSULTING AS?

BORCH CONSULTING AS
NOK 314,000 rev. · NOK 310,000 profit

BORCH CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORCH CONSULTING AS

Who owns BORCH CONSULTING AS?

Hans Gustav Borch is the largest registered owner, with 100.0%.

What is the revenue of BORCH CONSULTING AS?

BORCH CONSULTING AS had revenue of NOK 314,000 in 2025.

Who is the general manager of BORCH CONSULTING AS?

Hans Gustav Borch is registered as general manager of BORCH CONSULTING AS.

Where is BORCH CONSULTING AS based?

BORCH CONSULTING AS has its business address in Jevnaker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.