BIZTRAC BETA
Computer programming activities

EMBOT AS

Org. no. 928469115 Limited company (AS) Ås Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −7,000
Equity NOK 22,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

EMBOT AS is registered as a limited company in Ås, Akershus with organisation number 928469115. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Salg av konsulenttjenester innen programmering, elektronikk, mekanikk, prototyping og produktutvikling. Utvikling av egne produkter for intern kompetanseheving, promotering og salg.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −7,000
Equity
NOK 22,000
Est. value
NOK 1.7m

Financial health · 2025

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

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

Who owns EMBOT AS?

SEEBERG STENERSEN HOLDING AS
EMBOT AS
NOK 1.0m rev. · NOK −7,000 profit

EMBOT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EMBOT AS

Who owns EMBOT AS?

SEEBERG STENERSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of EMBOT AS?

EMBOT AS had revenue of NOK 1.0m in 2025.

Who is the general manager of EMBOT AS?

Henning Seeberg Stenersen is registered as general manager of EMBOT AS.

Where is EMBOT AS based?

EMBOT AS has its business address in Ski.

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.