BIZTRAC BETA
Construction of residential and non-residential buildings

SVENDSBY BYGG AS

Org. no. 916765185 Limited company (AS) Halden Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 5.5m
Operating profit NOK 333,000
Equity NOK 916,000
Incorporated 2016
Employees 6
Share capital NOK 40,000

SVENDSBY BYGG AS is registered as a limited company in Halden, Østfold with organisation number 916765185. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016 and has 6 registered employees. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Tømrertjenester innen rehabilitering, nybygg, omgjøringer av bygninger mv. Herunder kjøp og salg av varer og tjenester i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.5m in revenue and NOK 333,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.5m
Operating profit
NOK 333,000
Equity
NOK 916,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns SVENDSBY BYGG AS?

OLE MORTEN SVENDSBY
SVENDSBY BYGG AS
NOK 5.5m rev. · NOK 333,000 profit

SVENDSBY BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVENDSBY BYGG AS

Who owns SVENDSBY BYGG AS?

OLE MORTEN SVENDSBY is the largest registered owner, with 100.0%.

What is the revenue of SVENDSBY BYGG AS?

SVENDSBY BYGG AS had revenue of NOK 5.5m in 2024.

Who is the general manager of SVENDSBY BYGG AS?

Ole Morten Svendsby is registered as general manager of SVENDSBY BYGG AS.

Where is SVENDSBY BYGG AS based?

SVENDSBY BYGG AS has its business address in Halden.

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.