biztrac. BETA
COMPANY REGISTER PROFILE
935919754 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of automotive fuel

MOSJØEN SERVICENTER AS

Org. no. 935919754 Limited company (AS) Vefsn Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 49.6m
Operating profit NOK 1.3m
Equity NOK 765,000
Incorporated 2025
Employees 28
Share capital NOK 30,000

MOSJØEN SERVICENTER AS is registered as a limited company in Vefsn, Nordland with organisation number 935919754. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2025 and has 28 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Handel, eventuelt å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 49.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 49.6m
Operating profit
NOK 1.3m
Equity
NOK 765,000
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
3.0%
Weak
Equity as a share of total capital

Who owns MOSJØEN SERVICENTER AS?

MOSJØEN SERVICENTER AS
NOK 49.6m rev. · NOK 1.3m profit

MOSJØEN SERVICENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOSJØEN SERVICENTER AS

Who owns MOSJØEN SERVICENTER AS?

STIL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MOSJØEN SERVICENTER AS?

MOSJØEN SERVICENTER AS had revenue of NOK 49.6m in 2025.

Who is the general manager of MOSJØEN SERVICENTER AS?

Trine Larem Olsen is registered as general manager of MOSJØEN SERVICENTER AS.

Where is MOSJØEN SERVICENTER AS based?

MOSJØEN SERVICENTER AS has its business address in Mosjøen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.