BIZTRAC BETA
Buying and selling of own real estate

SEMSBYVEIEN 71B AS

Org. no. 922720185 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −39,000
Equity NOK −981,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−981k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−39k kr).

SEMSBYVEIEN 71B AS is registered as a limited company in Tønsberg, Vestfold with organisation number 922720185. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, utvikling av fast eiendom samt utleie av fast eiendom og alt som står i den forbindelse”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −39,000
Equity
NOK −981,000

Financial health · 2025

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

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

Who owns SEMSBYVEIEN 71B AS?

TOMMY B. HOLDING AS
SEMSBYVEIEN 71B AS
NOK 0 rev. · NOK −39,000 profit

SEMSBYVEIEN 71B AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEMSBYVEIEN 71B AS

Who owns SEMSBYVEIEN 71B AS?

TOMMY B. HOLDING AS is the largest registered owner, with 52.7%.

What is the revenue of SEMSBYVEIEN 71B AS?

SEMSBYVEIEN 71B AS had revenue of NOK 0 in 2025.

Where is SEMSBYVEIEN 71B AS based?

SEMSBYVEIEN 71B AS has its business address in Vear.

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.