BIZTRAC BETA
Other real estate activities on a fee or contract basis

BORGIN HOLDING AS

Org. no. 990250731 Limited company (AS) Seljord Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 64,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

BORGIN HOLDING AS is registered as a limited company in Seljord, Telemark with organisation number 990250731. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i finans- og realobjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 64,000
Est. value
NOK 904,000

Financial health · 2024

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

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

Who owns BORGIN HOLDING AS?

TOMMY LAUVSTAD
BORGIN HOLDING AS
NOK 0 rev. · NOK −26,000 profit

BORGIN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BORGIN HOLDING AS own?

BORGIN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BORGIN HOLDING AS

Who owns BORGIN HOLDING AS?

TOMMY LAUVSTAD is the largest registered owner, with 100.0%.

What is the revenue of BORGIN HOLDING AS?

BORGIN HOLDING AS had revenue of NOK 0 in 2025.

Where is BORGIN HOLDING AS based?

BORGIN HOLDING AS has its business address in Seljord.

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.