BIZTRAC BETA
COMPANY REGISTER PROFILE
914414725 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

EPAG AS

Org. no. 914414725 Limited company (AS) Vestby Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK −16,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−16k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

EPAG AS is registered as a limited company in Vestby, Akershus with organisation number 914414725. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i verdipapirer og fast eiendom.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK −16,000

Financial health · 2025

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

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

Who owns EPAG AS?

EPAG AS
· NOK −4,000 profit

EPAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EPAG AS

Who owns EPAG AS?

ANDREAS NIKOLAI LYDERSEN is the largest registered owner, with 100.0%.

Where is EPAG AS based?

EPAG AS has its business address in Son.

Property

Business address Soltoppveien 4B, 1553 Son
Cadastral unit 3216-135/582/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.