biztrac. BETA
COMPANY REGISTER PROFILE
981919173 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of information and communication equipment

SAFE CONSULTING AS

Org. no. 981919173 Limited company (AS) Fredrikstad Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK −2.9m
Equity NOK 8.9m
Incorporated 2000
Share capital NOK 5.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,9 mill kr).

SAFE CONSULTING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 981919173. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2000. Registered share capital is NOK 5.0m, divided into 50000 shares. The company's stated purpose is: “Salg og konsulentvirksomhet innen IT, samt annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK −2.9m in operating profit.

Former names: INVESTECH AS

Key figures · 2025

Revenue
NOK 3.3m
▼ −31 %
Operating profit
NOK −2.9m
▼ −16 %
Equity
NOK 8.9m
▼ −23 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
4.23
Very good
Current assets ÷ current liabilities
Profitability
-21.4%
Not satisfactory
Return on total assets
Solidity
76.5%
Very good
Equity as a share of total capital

Who owns SAFE CONSULTING AS?

SAFE CONSULTING AS
NOK 3.3m rev. · NOK −2.9m profit

SAFE CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAFE CONSULTING AS

Who owns SAFE CONSULTING AS?

ODA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SAFE CONSULTING AS?

SAFE CONSULTING AS had revenue of NOK 3.3m in 2025.

Where is SAFE CONSULTING AS based?

SAFE CONSULTING AS has its business address in Torp.

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.