BIZTRAC BETA
Office administrative and support activities

SMEDAAS RÅDGIVNING AS

Org. no. 928154866 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −51,000
Equity NOK 1.1m
Incorporated 2021
Share capital NOK 30,000

Signals

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

SMEDAAS RÅDGIVNING AS is registered as a limited company in Drammen, Buskerud with organisation number 928154866. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet, samt kjøp og salg av aksjer mm.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −51,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −51,000
Equity
NOK 1.1m
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
12.79
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.2%
Very good
Equity as a share of total capital

Who owns SMEDAAS RÅDGIVNING AS?

LISBET KARI SMEDAAS WØLNER
SMEDAAS RÅDGIVNING AS
NOK 0 rev. · NOK −51,000 profit

SMEDAAS RÅDGIVNING AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMEDAAS RÅDGIVNING AS

Who owns SMEDAAS RÅDGIVNING AS?

LISBET KARI SMEDAAS WØLNER is the largest registered owner, with 60.0%.

What is the revenue of SMEDAAS RÅDGIVNING AS?

SMEDAAS RÅDGIVNING AS had revenue of NOK 0 in 2025.

Who is the general manager of SMEDAAS RÅDGIVNING AS?

Lisbet Kari Smedaas Wølner is registered as general manager of SMEDAAS RÅDGIVNING AS.

Where is SMEDAAS RÅDGIVNING AS based?

SMEDAAS RÅDGIVNING AS has its business address in Drammen.

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.