BIZTRAC BETA
Rental and operating of own or leased real estate

SEMSBYEN AS

Org. no. 918257748 Limited company (AS) Tønsberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 4.6m
Equity NOK 10.2m
Incorporated 2016
Share capital NOK 10.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SEMSBYEN AS is registered as a limited company in Tønsberg, Vestfold with organisation number 918257748. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Investeringer i fast eiendom og eiendomsaksjer, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 4.6m in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 4.6m
Equity
NOK 10.2m
Est. value
NOK 13.5m

Financial health · 2024

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.3%
Satisfactory
Equity as a share of total capital

Who owns SEMSBYEN AS?

BJARØY EIENDOM AS
SEMSBYEN AS
NOK 8.5m rev. · NOK 4.6m profit

SEMSBYEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SEMSBYEN AS er morselskap for 15 datterselskaper:

Frequently asked questions about SEMSBYEN AS

Who owns SEMSBYEN AS?

BJARØY EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SEMSBYEN AS?

SEMSBYEN AS had revenue of NOK 8.5m in 2024.

Who is the general manager of SEMSBYEN AS?

Christoffer Jonstang is registered as general manager of SEMSBYEN AS.

Where is SEMSBYEN AS based?

SEMSBYEN AS has its business address in Tønsberg.

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.