biztrac. BETA
COMPANY REGISTER PROFILE
931211293 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BORRO PARTNER HOLDING AS

Org. no. 931211293 Limited company (AS) Larvik Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 68,000
Incorporated 2023
Share capital NOK 800,000

Signals

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

BORRO PARTNER HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 931211293. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 800,000, divided into 80000 shares. The company's stated purpose is: “Investere i selskaper og eiendom, samt andre aktiviteter knyttet til kjøp og salg av aksjer.”.

Key figures · 2025

Operating profit
NOK −13,000
▼ −7 %
Equity
NOK 68,000
▼ −91 %
Est. value
NOK 80,000

Financial health · 2025

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

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

Who owns BORRO PARTNER HOLDING AS?

BORRO PARTNER HOLDING AS
· NOK −13,000 profit

BORRO PARTNER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BORRO PARTNER HOLDING AS own?

BORRO PARTNER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BORRO PARTNER HOLDING AS

Who owns BORRO PARTNER HOLDING AS?

Martin Dybwad is the largest registered owner, with 100.0%.

Who is the general manager of BORRO PARTNER HOLDING AS?

Martin Dybwad is registered as general manager of BORRO PARTNER HOLDING AS.

Where is BORRO PARTNER HOLDING AS based?

BORRO PARTNER HOLDING AS has its business address in Stavern.

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.