biztrac. BETA
COMPANY REGISTER PROFILE
931843060 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Security activities n.e.c.

ENFORZO AS

Org. no. 931843060 Limited company (AS) Sunnfjord Incorporated 2023 Active
Revenue 2025 NOK 191,000
Operating profit NOK −62,000
Equity NOK −165,000
Incorporated 2023
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−165k kr).

ENFORZO AS is registered as a limited company in Sunnfjord, Vestland with organisation number 931843060. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av varer og tjenester innenfor sikkerhetssegmentet, herunder vektertjenester og alarmanlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 191,000 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 191,000
▲ +94 %
Operating profit
NOK −62,000
▲ +42 %
Equity
NOK −165,000
▼ −60 %

Financial health · 2025

Liquidity
1.74
Good
Current assets ÷ current liabilities
Profitability
-82.2%
Not satisfactory
Return on total assets
Solidity
-154.1%
Weak
Equity as a share of total capital

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

Who owns ENFORZO AS?

ENFORZO AS
NOK 191,000 rev. · NOK −62,000 profit

ENFORZO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENFORZO AS

Who owns ENFORZO AS?

David Nilsen is the largest registered owner, with 70.0%.

What is the revenue of ENFORZO AS?

ENFORZO AS had revenue of NOK 191,000 in 2025.

Who is the general manager of ENFORZO AS?

David Nilsen is registered as general manager of ENFORZO AS.

Where is ENFORZO AS based?

ENFORZO AS has its business address in Førde.

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.