BIZTRAC BETA
Business and other management consultancy activities

SMECO AS

Org. no. 924421169 Limited company (AS) Ulstein Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 456,000
Operating profit NOK −7,000
Equity NOK 162,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

SMECO AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 924421169. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Administrativ koordinering av faglig, vitenskapelig og teknisk virksomhet. Selskapet skal også yte rådgiving knyttet til teknologiske utviklingsprosjekter, primært innenfor havrommet. Selskapet kan delta i andre selskaper gjennom investeringer i aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 456,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 456,000
Operating profit
NOK −7,000
Equity
NOK 162,000
Est. value
NOK 558,000

Financial health · 2024

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

Who owns SMECO AS?

SYNNØVE ASBJØRG RINGSTAD INGEBERG
SMECO AS
NOK 456,000 rev. · NOK −7,000 profit

SMECO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMECO AS

Who owns SMECO AS?

SYNNØVE ASBJØRG RINGSTAD INGEBERG is the largest registered owner, with 50.0%.

What is the revenue of SMECO AS?

SMECO AS had revenue of NOK 456,000 in 2024.

Where is SMECO AS based?

SMECO AS has its business address in Ulsteinvik.

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.