BIZTRAC BETA
Buying and selling of own real estate

SMEDVEIEN 7 AS

Org. no. 928107159 Limited company (AS) Stjørdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 22,000
Operating profit NOK −52,000
Equity NOK −150,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

SMEDVEIEN 7 AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 928107159. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Erverve, eie, utvikle og forvalte eiendom, og alt hva dermed står i forbindelse. Selskapet kan med aksjeinnskudd eller på annen måte delta i virksomhet med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 22,000 in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 22,000
Operating profit
NOK −52,000
Equity
NOK −150,000

Financial health · 2025

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

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

Who owns SMEDVEIEN 7 AS?

KROFU AS
SMEDVEIEN 7 AS
NOK 22,000 rev. · NOK −52,000 profit

SMEDVEIEN 7 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMEDVEIEN 7 AS

Who owns SMEDVEIEN 7 AS?

KROFU AS is the largest registered owner, with 50.0%.

What is the revenue of SMEDVEIEN 7 AS?

SMEDVEIEN 7 AS had revenue of NOK 22,000 in 2025.

Where is SMEDVEIEN 7 AS based?

SMEDVEIEN 7 AS has its business address in Stjørdal.

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.