biztrac. BETA
COMPANY REGISTER PROFILE
931491776 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

SE-TA PROJECT AS

Org. no. 931491776 Limited company (AS) Surnadal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 21.9m
Operating profit NOK −749,000
Equity NOK 1.6m
Incorporated 2023
Share capital NOK 2.0m

Signals

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

SE-TA PROJECT AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 931491776. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 2.0m, divided into 20000 shares. The company's stated purpose is: “Kjøp, utvikling, drift, forvaltning og salg av fast eiendom, samt det som naturlig står i forhold til dette, herunder også deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.9m in revenue and NOK −749,000 in operating profit.

Key figures · 2025

Revenue
NOK 21.9m
▲ +193 %
Operating profit
NOK −749,000
▼ −215 %
Equity
NOK 1.6m
▼ −35 %
Est. value
NOK 34.0m

Financial health · 2025

Liquidity
12.58
Very good
Current assets ÷ current liabilities
Profitability
-4.5%
Not satisfactory
Return on total assets
Solidity
23.5%
Good
Equity as a share of total capital

Who owns SE-TA PROJECT AS?

SE-TA PROJECT AS
NOK 21.9m rev. · NOK −749,000 profit

SE-TA PROJECT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SE-TA PROJECT AS

Who owns SE-TA PROJECT AS?

SETRA SURNA AS is the largest registered owner, with 50.0%.

What is the revenue of SE-TA PROJECT AS?

SE-TA PROJECT AS had revenue of NOK 21.9m in 2025.

Where is SE-TA PROJECT AS based?

SE-TA PROJECT AS has its business address in Surnadal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.