BIZTRAC BETA
Other printing

SVENDSEN PROFIL AS

Org. no. 825589732 Limited company (AS) Indre Østfold Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK −235,000
Equity NOK 668,000
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−235k kr).

SVENDSEN PROFIL AS is registered as a limited company in Indre Østfold, Østfold with organisation number 825589732. The business is classified under other printing (NACE 18.120). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er profilering, herunder trykking, firmagaver, skilt og dekor, samt eie aksjer i andre selskaper, og annet som naturlig hører til denne virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK −235,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK −235,000
Equity
NOK 668,000
Est. value
NOK 3.2m

Financial health · 2024

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.2%
Good
Equity as a share of total capital

Who owns SVENDSEN PROFIL AS?

TOMMY SVENDSEN
SVENDSEN PROFIL AS
NOK 5.3m rev. · NOK −235,000 profit

SVENDSEN PROFIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVENDSEN PROFIL AS

Who owns SVENDSEN PROFIL AS?

TOMMY SVENDSEN is the largest registered owner, with 100.0%.

What is the revenue of SVENDSEN PROFIL AS?

SVENDSEN PROFIL AS had revenue of NOK 5.3m in 2024.

Who is the general manager of SVENDSEN PROFIL AS?

Tommy Svendsen is registered as general manager of SVENDSEN PROFIL AS.

Where is SVENDSEN PROFIL AS based?

SVENDSEN PROFIL AS has its business address in Mysen.

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.