BIZTRAC BETA
Computer consultancy and computer facilities management activities

FLUXUS LOGICAE AS

Org. no. 930875295 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.1m
Equity NOK 916,000
Incorporated 2023
Share capital NOK 30,000

FLUXUS LOGICAE AS is registered as a limited company in Oslo, Oslo with organisation number 930875295. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen IT-konsulent - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.1m
Equity
NOK 916,000
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns FLUXUS LOGICAE AS?

A S M SAMIUL SAKI CHOWDHURY
FLUXUS LOGICAE AS
NOK 2.2m rev. · NOK 1.1m profit

FLUXUS LOGICAE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLUXUS LOGICAE AS own?

FLUXUS LOGICAE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FLUXUS LOGICAE AS

Who owns FLUXUS LOGICAE AS?

A S M SAMIUL SAKI CHOWDHURY is the largest registered owner, with 100.0%.

What is the revenue of FLUXUS LOGICAE AS?

FLUXUS LOGICAE AS had revenue of NOK 2.2m in 2025.

Where is FLUXUS LOGICAE AS based?

FLUXUS LOGICAE AS has its business address in Oslo.

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.