BIZTRAC BETA
Computer programming activities

EMBED AS

Org. no. 925272981 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 89,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

EMBED AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925272981. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i andre selskaper, samt å tilby konsulenttjenester innen integrerte datasystemer og informasjonsteknologi, inkludert drift og utvikling av egne og andres digitale løsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 89,000
Est. value
NOK 162,000

Financial health · 2025

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

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

Who owns EMBED AS?

SIGURD MØRKVED ALBREKTSEN
EMBED AS
NOK 0 rev. · NOK −16,000 profit

EMBED AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EMBED AS own?

EMBED AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EMBED AS

Who owns EMBED AS?

SIGURD MØRKVED ALBREKTSEN is the largest registered owner, with 100.0%.

What is the revenue of EMBED AS?

EMBED AS had revenue of NOK 0 in 2025.

Where is EMBED AS based?

EMBED AS has its business address in Trondheim.

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.