biztrac. BETA
COMPANY REGISTER PROFILE
926597159 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SUNBELT HOLDING AS

Org. no. 926597159 Limited company (AS) Notodden Incorporated 2021 Active
Operating profit NOK −54,000
Equity NOK 65.4m
Incorporated 2021
Share capital NOK 175,000

Signals

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

SUNBELT HOLDING AS is registered as a limited company in Notodden, Telemark with organisation number 926597159. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 175,000, divided into 625 shares. The company's stated purpose is: “Eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −54,000
▼ −7 %
Equity
NOK 65.4m
▲ +50 %
Est. value
NOK 127.0m

Financial health · 2025

Liquidity
107.27
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
99.2%
Very good
Equity as a share of total capital

Who owns SUNBELT HOLDING AS?

SUNBELT HOLDING AS
· NOK −54,000 profit

SUNBELT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SUNBELT HOLDING AS own?

SUNBELT HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SUNBELT HOLDING AS

Who owns SUNBELT HOLDING AS?

Steinar Kristian Kvamme is the largest registered owner, with 100.0%.

Who is the general manager of SUNBELT HOLDING AS?

Steinar Kristian Kvamme is registered as general manager of SUNBELT HOLDING AS.

Where is SUNBELT HOLDING AS based?

SUNBELT HOLDING AS has its business address in Notodden.

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.