BIZTRAC BETA
COMPANY REGISTER PROFILE
825777032 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TRÆLAND HOLDING AS

Org. no. 825777032 Limited company (AS) Kvinesdal Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −6,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−6k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

TRÆLAND HOLDING AS is registered as a limited company in Kvinesdal, Agder with organisation number 825777032. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −9,000
Equity
NOK −6,000

Financial health · 2024

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

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

Who owns TRÆLAND HOLDING AS?

TRÆLAND HOLDING AS
· NOK −9,000 profit

TRÆLAND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRÆLAND HOLDING AS

Who owns TRÆLAND HOLDING AS?

GORD KÅRE TRÆLAND is the largest registered owner, with 100.0%.

Where is TRÆLAND HOLDING AS based?

TRÆLAND HOLDING AS has its business address in Kvinesdal.

Property

Business address Jerstadveien 160, 4480 Kvinesdal
Cadastral unit 4227-88/25/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.