biztrac. BETA
COMPANY REGISTER PROFILE
822977472 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ESE SOLUTIONS AS

Org. no. 822977472 Limited company (AS) Stavanger Incorporated 2019 Active
Revenue 2025 NOK 4.2m
Operating profit NOK 413,000
Equity NOK 3.2m
Incorporated 2019
Share capital NOK 30,000

ESE SOLUTIONS AS is registered as a limited company in Stavanger, Rogaland with organisation number 822977472. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, utvikle og selge produkter og teknologi, selskaper og eiendom samt hva som står i forbindelse med dette. Delta i øvrig virksomhet hva hermed er forbundet med.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 413,000 in operating profit.

Former names: FOLKETTI HOLDING AS

Key figures · 2025

Revenue
NOK 4.2m
▲ +9 %
Operating profit
NOK 413,000
▼ −76 %
Equity
NOK 3.2m
▲ +9 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
0.60
Weak
Current assets ÷ current liabilities
Profitability
10.2%
Good
Return on total assets
Solidity
73.4%
Very good
Equity as a share of total capital

Who owns ESE SOLUTIONS AS?

ESE SOLUTIONS AS
NOK 4.2m rev. · NOK 413,000 profit

ESE SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESE SOLUTIONS AS own?

ESE SOLUTIONS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESE SOLUTIONS AS

Who owns ESE SOLUTIONS AS?

Rune Martin Folkestad is the largest registered owner, with 100.0%.

What is the revenue of ESE SOLUTIONS AS?

ESE SOLUTIONS AS had revenue of NOK 4.2m in 2025.

Where is ESE SOLUTIONS AS based?

ESE SOLUTIONS AS has its business address in Stavanger.

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.