biztrac. BETA
COMPANY REGISTER PROFILE
913682394 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other specialised construction activities in construction of buildings

PUENTE HOLDING AS

Org. no. 913682394 Limited company (AS) Lillestrøm Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −43,000
Equity NOK 10.5m
Incorporated 2014
Share capital NOK 72,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−43k kr).

PUENTE HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 913682394. The business is classified under other specialised construction activities in construction of buildings (NACE 43.420). The company was incorporated in 2014. Registered share capital is NOK 72,000, divided into 720 shares. The company's stated purpose is: “Investering i andre selskaper og aksjer, samt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −43,000
▼ −32 %
Equity
NOK 10.5m
▲ +5 %
Est. value
NOK 7.5m

Financial health · 2025

Liquidity
9.36
Very good
Current assets ÷ current liabilities
Profitability
5.0%
Weak
Return on total assets
Solidity
89.4%
Very good
Equity as a share of total capital

Who owns PUENTE HOLDING AS?

PUENTE HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PUENTE HOLDING AS own?

PUENTE HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

PUENTE HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about PUENTE HOLDING AS

Who owns PUENTE HOLDING AS?

Juan Antonio Puente is the largest registered owner, with 80.0%.

Who is the general manager of PUENTE HOLDING AS?

Juan Antonio Puente is registered as general manager of PUENTE HOLDING AS.

Where is PUENTE HOLDING AS based?

PUENTE HOLDING AS has its business address in Blaker.

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.