BIZTRAC BETA
COMPANY REGISTER PROFILE
921269730 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

ING. BORGEN AS

Org. no. 921269730 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 821,000
Operating profit NOK 15,000
Equity NOK 46,000
Incorporated 2018
Share capital NOK 30,000

ING. BORGEN AS is registered as a limited company in Oslo, Oslo with organisation number 921269730. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tekniske ingeniørtjenester, prosjektering, konsulentarbeid, veiledning, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 821,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 821,000
Operating profit
NOK 15,000
Equity
NOK 46,000
Est. value
NOK 97,000

Financial health · 2024

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ING. BORGEN AS?

MAGNUS HAREGG BORGEN
ING. BORGEN AS
NOK 821,000 rev. · NOK 15,000 profit

ING. BORGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ING. BORGEN AS

Who owns ING. BORGEN AS?

MAGNUS HAREGG BORGEN is the largest registered owner, with 100.0%.

What is the revenue of ING. BORGEN AS?

ING. BORGEN AS had revenue of NOK 821,000 in 2024.

Who is the general manager of ING. BORGEN AS?

Magnus Haregg Borgen is registered as general manager of ING. BORGEN AS.

Where is ING. BORGEN AS based?

ING. BORGEN 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.