BIZTRAC BETA
Uoppgitt

ENGQVIST INVEST AS

Org. no. 929430778 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 15,000
Incorporated 2022
Share capital NOK 4.4m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

ENGQVIST INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929430778. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 4.4m, divided into 4430 shares. The company's stated purpose is: “Kjøp, salg og investering i aksjer, andre verdipapirer og fast eiendom, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 15,000
Est. value
NOK 17,000

Financial health · 2024

Liquidity
-354.98
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.3%
Weak
Equity as a share of total capital

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

Who owns ENGQVIST INVEST AS?

BO NICLAS ENGKVIST
ENGQVIST INVEST AS
NOK 0 rev. · NOK −6,000 profit

ENGQVIST INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGQVIST INVEST AS

Who owns ENGQVIST INVEST AS?

BO NICLAS ENGKVIST is the largest registered owner, with 100.0%.

What is the revenue of ENGQVIST INVEST AS?

ENGQVIST INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of ENGQVIST INVEST AS?

Bo Niclas Engkvist is registered as general manager of ENGQVIST INVEST AS.

Where is ENGQVIST INVEST AS based?

ENGQVIST INVEST AS has its business address in Trondheim.

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.