biztrac. BETA
COMPANY REGISTER PROFILE
928567788 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

EFY INVEST AS

Org. no. 928567788 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 585,000
Operating profit NOK 565,000
Equity NOK 1.4m
Incorporated 2021
Share capital NOK 35,000

Signals

1 flags
  • Nylig endring 2026-07-07 Aksjekapital registrert 2026-07-07.

EFY INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 928567788. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 35,000, divided into 1 shares. The company's stated purpose is: “Eie aksjer og/eller andeler i PricewaterhouseCoopers, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 585,000 in revenue and NOK 565,000 in operating profit.

Key figures · 2025

Revenue
NOK 585,000
▲ +100 %
Operating profit
NOK 565,000
▲ +103 %
Equity
NOK 1.4m
▲ +65 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
37.4%
Very good
Return on total assets
Solidity
89.6%
Very good
Equity as a share of total capital

Who owns EFY INVEST AS?

EFY INVEST AS
NOK 585,000 rev. · NOK 565,000 profit

EFY INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EFY INVEST AS own?

EFY INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EFY INVEST AS

Who owns EFY INVEST AS?

Eivind Faafeng Falck-Ytter is the largest registered owner, with 100.0%.

What is the revenue of EFY INVEST AS?

EFY INVEST AS had revenue of NOK 585,000 in 2025.

Where is EFY INVEST AS based?

EFY INVEST AS has its business address in Stabekk.

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.