BIZTRAC BETA
Computer programming activities

SEMA PROTECTION AS

Org. no. 825637222 Limited company (AS) Sandnes Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK −12,000
Equity NOK 33,000
Incorporated 2020
Share capital NOK 100,000

Signals

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

SEMA PROTECTION AS is registered as a limited company in Sandnes, Rogaland with organisation number 825637222. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utvikle og kommersialisere tekniske industrielle innovasjons løsninger rettet mot miljø- og naturtrusler, samt annet som naturlig faller inn under med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −12,000
Equity
NOK 33,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns SEMA PROTECTION AS?

TEX INVENTIONS AS
SEMA PROTECTION AS
NOK 5,000 rev. · NOK −12,000 profit

SEMA PROTECTION AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEMA PROTECTION AS

Who owns SEMA PROTECTION AS?

TEX INVENTIONS AS is the largest registered owner, with 60.0%.

What is the revenue of SEMA PROTECTION AS?

SEMA PROTECTION AS had revenue of NOK 5,000 in 2025.

Where is SEMA PROTECTION AS based?

SEMA PROTECTION AS has its business address in Sandnes.

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.