BIZTRAC BETA
Rental and operating of own or leased real estate

SEMSBYVEIEN 116 AS

Org. no. 928869482 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK −9,000
Operating profit NOK −89,000
Equity NOK 30,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SEMSBYVEIEN 116 AS is registered as a limited company in Tønsberg, Vestfold with organisation number 928869482. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK −9,000 in revenue and NOK −89,000 in operating profit.

Key figures · 2025

Revenue
NOK −9,000
Operating profit
NOK −89,000
Equity
NOK 30,000
Est. value
NOK 27,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SEMSBYVEIEN 116 AS?

LHH HOLDING AS
SEMSBYVEIEN 116 AS
NOK −9,000 rev. · NOK −89,000 profit

SEMSBYVEIEN 116 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SEMSBYVEIEN 116 AS er morselskap for 1 datterselskap:

Frequently asked questions about SEMSBYVEIEN 116 AS

Who owns SEMSBYVEIEN 116 AS?

LHH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SEMSBYVEIEN 116 AS?

SEMSBYVEIEN 116 AS had revenue of NOK −9,000 in 2025.

Where is SEMSBYVEIEN 116 AS based?

SEMSBYVEIEN 116 AS has its business address in Sem.

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.