BIZTRAC BETA
Industrial product and fashion design activities

3DPS AS

Org. no. 832501832 Limited company (AS) Ås Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 182,000
Operating profit NOK −19,000
Equity NOK 19,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

3DPS AS is registered as a limited company in Ås, Akershus with organisation number 832501832. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen industridesign - 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 182,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 182,000
Operating profit
NOK −19,000
Equity
NOK 19,000
Est. value
NOK 201,000

Financial health · 2025

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

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

Who owns 3DPS AS?

PER STEINAR KOTANI HOFTUN
3DPS AS
NOK 182,000 rev. · NOK −19,000 profit

3DPS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 3DPS AS

Who owns 3DPS AS?

PER STEINAR KOTANI HOFTUN is the largest registered owner, with 100.0%.

What is the revenue of 3DPS AS?

3DPS AS had revenue of NOK 182,000 in 2025.

Who is the general manager of 3DPS AS?

Per Steinar Kotani Hoftun is registered as general manager of 3DPS AS.

Where is 3DPS AS based?

3DPS AS has its business address in Ås.

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.