BIZTRAC BETA
Rental and operating of own or leased real estate

DECUSSATUS AS

Org. no. 890695582 Limited company (AS) Øygarden Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 502,000
Operating profit NOK 42,000
Equity NOK 9.3m
Incorporated 2006
Share capital NOK 200,000

DECUSSATUS AS is registered as a limited company in Øygarden, Vestland with organisation number 890695582. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 50 shares. The company's stated purpose is: “Konsulentbistand innen sjømat, båtutleie samt investering i eiendom og verdipapirer, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 502,000 in revenue and NOK 42,000 in operating profit.

Key figures · 2024

Revenue
NOK 502,000
Operating profit
NOK 42,000
Equity
NOK 9.3m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns DECUSSATUS AS?

ODD EINAR TUFTELAND
DECUSSATUS AS
NOK 502,000 rev. · NOK 42,000 profit

DECUSSATUS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DECUSSATUS AS own?

DECUSSATUS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DECUSSATUS AS

Who owns DECUSSATUS AS?

ODD EINAR TUFTELAND is the largest registered owner, with 100.0%.

What is the revenue of DECUSSATUS AS?

DECUSSATUS AS had revenue of NOK 502,000 in 2024.

Who is the general manager of DECUSSATUS AS?

Odd Einar Tufteland is registered as general manager of DECUSSATUS AS.

Where is DECUSSATUS AS based?

DECUSSATUS AS has its business address in Bjørøyhamn.

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.