BIZTRAC BETA
Other activities auxiliary to financial services, except insurance and pension funding

PROFIN AS

Org. no. 931788000 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK −671,000
Equity NOK 650,000
Incorporated 2023
Share capital NOK 33,000

Signals

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

PROFIN AS is registered as a limited company in Lillestrøm, Akershus with organisation number 931788000. The business is classified under other activities auxiliary to financial services, except insurance and pension funding (NACE 66.190). The company was incorporated in 2023. Registered share capital is NOK 33,000, divided into 111 shares. The company's stated purpose is: “Formidle finansielle produkter og forsikringer, samt annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK −671,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK −671,000
Equity
NOK 650,000
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns PROFIN AS?

BRODERSEN HOLDING AS
PROFIN AS
NOK 4.2m rev. · NOK −671,000 profit

PROFIN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROFIN AS

Who owns PROFIN AS?

BRODERSEN HOLDING AS is the largest registered owner, with 88.3%.

What is the revenue of PROFIN AS?

PROFIN AS had revenue of NOK 4.2m in 2025.

Who is the general manager of PROFIN AS?

Morten Tollefsen Brodersen is registered as general manager of PROFIN AS.

Where is PROFIN AS based?

PROFIN AS has its business address in Lillestrøm.

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.