BIZTRAC BETA
Construction of residential and non-residential buildings

EPS-BYGG AS

Org. no. 936459072 Limited company (AS) Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 459,000
Equity NOK 388,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-23.

EPS-BYGG AS is registered as a limited company in Bø, Nordland with organisation number 936459072. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen oppføring av bygninger og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 459,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 459,000
Equity
NOK 388,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.4%
Very good
Equity as a share of total capital

Who owns EPS-BYGG AS?

EGIDIJUS PIKAUSKAS-SENIK
EPS-BYGG AS
NOK 1.9m rev. · NOK 459,000 profit

EPS-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EPS-BYGG AS

Who owns EPS-BYGG AS?

EGIDIJUS PIKAUSKAS-SENIK is the largest registered owner, with 100.0%.

What is the revenue of EPS-BYGG AS?

EPS-BYGG AS had revenue of NOK 1.9m in 2025.

Who is the general manager of EPS-BYGG AS?

Egidijus Pikauskas-Senik is registered as general manager of EPS-BYGG AS.

Where is EPS-BYGG AS based?

EPS-BYGG AS has its business address in Straumsjøen.

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.