BIZTRAC BETA
Construction of residential and non-residential buildings

BALSWICK AS

Org. no. 992323566 Limited company (AS) Harstad Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK −53,000
Equity NOK 1.1m
Incorporated 2008
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−53k kr).

BALSWICK AS is registered as a limited company in Harstad, Troms with organisation number 992323566. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Virksomhet innen tømrerbransjen samt graving og transport. Samt salg av helseprodukter og helserådgivning. I tillegg til annen virksomhet som naturlig tilhører selskapet øvrige virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK −53,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK −53,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2024

Liquidity
0.66
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.0%
Very good
Equity as a share of total capital

Who owns BALSWICK AS?

TROND BALSWICK
BALSWICK AS
NOK 2.7m rev. · NOK −53,000 profit

BALSWICK AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BALSWICK AS

Who owns BALSWICK AS?

TROND BALSWICK is the largest registered owner, with 50.0%.

What is the revenue of BALSWICK AS?

BALSWICK AS had revenue of NOK 2.7m in 2024.

Who is the general manager of BALSWICK AS?

Trond Balswick is registered as general manager of BALSWICK AS.

Where is BALSWICK AS based?

BALSWICK AS has its business address in Harstad.

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.