BIZTRAC BETA
Joinery installation

EF-BYGG AS

Org. no. 936244149 Limited company (AS) Sveio Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 251,000
Operating profit NOK −42,000
Equity NOK −22,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−22k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−42k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-05.

EF-BYGG AS is registered as a limited company in Sveio, Vestland with organisation number 936244149. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Byggearbeid, renovering av bolig, innvendig og utvendig dekorasjon, møbelmontering.”. The most recent filed accounts, for the 2025 financial year, show NOK 251,000 in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 251,000
Operating profit
NOK −42,000
Equity
NOK −22,000

Financial health · 2025

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

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

Who owns EF-BYGG AS?

EVALDAS CEPAS
EF-BYGG AS
NOK 251,000 rev. · NOK −42,000 profit

EF-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EF-BYGG AS

Who owns EF-BYGG AS?

EVALDAS CEPAS is the largest registered owner, with 100.0%.

What is the revenue of EF-BYGG AS?

EF-BYGG AS had revenue of NOK 251,000 in 2025.

Who is the general manager of EF-BYGG AS?

Evaldas Cepas is registered as general manager of EF-BYGG AS.

Where is EF-BYGG AS based?

EF-BYGG AS has its business address in Førde I Hordaland.

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.