BIZTRAC BETA
Construction of residential and non-residential buildings

SJESPERSEN BYGG AS

Org. no. 921267738 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −21,000
Equity NOK 519,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

SJESPERSEN BYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921267738. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Hus og hyttebygging og det som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −21,000
Equity
NOK 519,000
Est. value
NOK 616,000

Financial health · 2025

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

Who owns SJESPERSEN BYGG AS?

CHRIS ANDRÉ JESPERSEN
SJESPERSEN BYGG AS
NOK 1.1m rev. · NOK −21,000 profit

SJESPERSEN BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SJESPERSEN BYGG AS

Who owns SJESPERSEN BYGG AS?

CHRIS ANDRÉ JESPERSEN is the largest registered owner, with 50.0%.

What is the revenue of SJESPERSEN BYGG AS?

SJESPERSEN BYGG AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SJESPERSEN BYGG AS?

Chris André Jespersen is registered as general manager of SJESPERSEN BYGG AS.

Where is SJESPERSEN BYGG AS based?

SJESPERSEN BYGG AS has its business address in Trondheim.

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.