biztrac. BETA
COMPANY REGISTER PROFILE
917799253 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

FLODIN DATA SYSTEMER AS

Org. no. 917799253 Limited company (AS) Fredrikstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 20.7m
Operating profit NOK 157,000
Equity NOK 1.3m
Incorporated 2016
Employees 8
Share capital NOK 30,000

FLODIN DATA SYSTEMER AS is registered as a limited company in Fredrikstad, Østfold with organisation number 917799253. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2016 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel og utvikling av dataprogrammer.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.7m in revenue and NOK 157,000 in operating profit.

Former names: NYE FLODIN DATA SYSTEMER AS

Key figures · 2025

Revenue
NOK 20.7m
▲ +5 %
Operating profit
NOK 157,000
▼ −85 %
Equity
NOK 1.3m
▼ −9 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
3.1%
Weak
Return on total assets
Solidity
25.6%
Good
Equity as a share of total capital

Who owns FLODIN DATA SYSTEMER AS?

FLODIN DATA SYSTEMER AS
NOK 20.7m rev. · NOK 157,000 profit

FLODIN DATA SYSTEMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLODIN DATA SYSTEMER AS

Who owns FLODIN DATA SYSTEMER AS?

FREDRIK FLODIN AS is the largest registered owner, with 100.0%.

What is the revenue of FLODIN DATA SYSTEMER AS?

FLODIN DATA SYSTEMER AS had revenue of NOK 20.7m in 2025.

Where is FLODIN DATA SYSTEMER AS based?

FLODIN DATA SYSTEMER AS has its business address in Fredrikstad.

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.