biztrac. BETA
COMPANY REGISTER PROFILE
927168596 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ENGFOLK AS

Org. no. 927168596 Limited company (AS) Lillesand Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 274,000
Incorporated 2021
Share capital NOK 515,000

Signals

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

ENGFOLK AS is registered as a limited company in Lillesand, Agder with organisation number 927168596. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 515,000, divided into 515 shares. The company's stated purpose is: “Gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
▲ +1 %
Equity
NOK 274,000
▼ −2 %
Est. value
NOK 322,000

Financial health · 2024

Liquidity
6.27
Very good
Current assets ÷ current liabilities
Profitability
-2.1%
Not satisfactory
Return on total assets
Solidity
89.2%
Very good
Equity as a share of total capital

Who owns ENGFOLK AS?

ENGFOLK AS
NOK 0 rev. · NOK −7,000 profit

ENGFOLK AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2022.

All shareholders and roles →

Which companies does ENGFOLK AS own?

ENGFOLK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENGFOLK AS

Who owns ENGFOLK AS?

Ola Engehagen is the largest registered owner, with 100.0%.

What is the revenue of ENGFOLK AS?

ENGFOLK AS had revenue of NOK 0 in 2024.

Where is ENGFOLK AS based?

ENGFOLK AS has its business address in Lillesand.

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.