biztrac. BETA
COMPANY REGISTER PROFILE
886618832 ORG. NO. 2021 ACCOUNTS 8 SECTIONS
Bankrupt UPDATED 03.10.2026
⚠SECORA AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Construction of water projects

SECORA AS

Org. no. 886618832 Limited company (AS) Vågan Incorporated 2004 Bankrupt
Revenue 2021 NOK 83.9m
Operating profit NOK −35.1m
Equity NOK −6.9m
Incorporated 2004
Share capital NOK 5.5m

Signals

1 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.

SECORA AS is registered as a limited company in Vågan, Nordland with organisation number 886618832. The business is classified under construction of water projects (NACE 42.910). The company was incorporated in 2004. Registered share capital is NOK 5.5m, divided into 550000 shares. The company's stated purpose is: “Utbygge og vedlikeholde fiskerihavner, farleder og annen virksomhet som står i sammenheng med dette.”. The most recent filed accounts, for the 2021 financial year, show NOK 83.9m in revenue and NOK −35.1m in operating profit.

Former names: TEKÅGEL INVEST XL AS

Key figures · 2021

Revenue
NOK 83.9m
▼ −8 %
Operating profit
NOK −35.1m
▼ −267 %
Equity
NOK −6.9m
▼ −122 %

Financial health · 2021

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
-51.8%
Not satisfactory
Return on total assets
Solidity
-12.2%
Weak
Equity as a share of total capital

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

Who owns SECORA AS?

No shareholders are registered for SECORA AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SECORA AS

What is the revenue of SECORA AS?

SECORA AS had revenue of NOK 83.9m in 2021.

Who is the general manager of SECORA AS?

Randi Johanne Lind is registered as general manager of SECORA AS.

Where is SECORA AS based?

SECORA AS has its business address in Svolvær.

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.