BIZTRAC BETA
Development of building projects

EPLEGRENDA AS

Org. no. 931566970 Limited company (AS) Kongsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 90,000
Operating profit NOK 56,000
Equity NOK 5,000
Incorporated 2023
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EPLEGRENDA AS is registered as a limited company in Kongsberg, Buskerud with organisation number 931566970. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utvikling, kjøp og salg av tomter og boliger.”. The most recent filed accounts, for the 2025 financial year, show NOK 90,000 in revenue and NOK 56,000 in operating profit.

Key figures · 2025

Revenue
NOK 90,000
Operating profit
NOK 56,000
Equity
NOK 5,000
Est. value
NOK 100,000

Financial health · 2025

Liquidity
27.63
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

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

Who owns EPLEGRENDA AS?

ENEO EIENDOM AS
EPLEGRENDA AS
NOK 90,000 rev. · NOK 56,000 profit

EPLEGRENDA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EPLEGRENDA AS

Who owns EPLEGRENDA AS?

ENEO EIENDOM AS is the largest registered owner, with 90.1%.

What is the revenue of EPLEGRENDA AS?

EPLEGRENDA AS had revenue of NOK 90,000 in 2025.

Who is the general manager of EPLEGRENDA AS?

Per Christian Vanebo is registered as general manager of EPLEGRENDA AS.

Where is EPLEGRENDA AS based?

EPLEGRENDA AS has its business address in Kongsberg.

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.