BIZTRAC BETA
Buying and selling of own real estate

SMIDSRØDVEIEN 4C AS

Org. no. 930362638 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 65,000
Operating profit NOK −268,000
Equity NOK 470,000
Incorporated 2022
Share capital NOK 516,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−268k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SMIDSRØDVEIEN 4C AS is registered as a limited company in Tønsberg, Vestfold with organisation number 930362638. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 516,000, divided into 6000 shares. The company's stated purpose is: “Utvikling, kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 65,000 in revenue and NOK −268,000 in operating profit.

Key figures · 2025

Revenue
NOK 65,000
Operating profit
NOK −268,000
Equity
NOK 470,000
Est. value
NOK 419,000

Financial health · 2025

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

Who owns SMIDSRØDVEIEN 4C AS?

TEIE BOLIG AS
SMIDSRØDVEIEN 4C AS
NOK 65,000 rev. · NOK −268,000 profit

SMIDSRØDVEIEN 4C AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SMIDSRØDVEIEN 4C AS er morselskap for 4 datterselskaper:

Frequently asked questions about SMIDSRØDVEIEN 4C AS

Who owns SMIDSRØDVEIEN 4C AS?

TEIE BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of SMIDSRØDVEIEN 4C AS?

SMIDSRØDVEIEN 4C AS had revenue of NOK 65,000 in 2025.

Where is SMIDSRØDVEIEN 4C AS based?

SMIDSRØDVEIEN 4C 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.