BIZTRAC BETA
Industrial product and fashion design activities

NANOSWIM AS

Org. no. 934983084 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 134,000
Operating profit NOK −111,000
Equity NOK −100,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−100k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−111k kr).

NANOSWIM AS is registered as a limited company in Bergen, Vestland with organisation number 934983084. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Faglig vitenskapelig og teknisk tjenesteyting.”. The most recent filed accounts, for the 2025 financial year, show NOK 134,000 in revenue and NOK −111,000 in operating profit.

Key figures · 2025

Revenue
NOK 134,000
Operating profit
NOK −111,000
Equity
NOK −100,000

Financial health · 2025

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-112.4%
Weak
Equity as a share of total capital

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

Who owns NANOSWIM AS?

BEHNOOD SJÅSTAD FATHI
NANOSWIM AS
NOK 134,000 rev. · NOK −111,000 profit

NANOSWIM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NANOSWIM AS

Who owns NANOSWIM AS?

BEHNOOD SJÅSTAD FATHI is the largest registered owner, with 50.0%.

What is the revenue of NANOSWIM AS?

NANOSWIM AS had revenue of NOK 134,000 in 2025.

Who is the general manager of NANOSWIM AS?

Thorolf Magnesen is registered as general manager of NANOSWIM AS.

Where is NANOSWIM AS based?

NANOSWIM AS has its business address in Blomsterdalen.

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.