BIZTRAC BETA
Retail sale of automotive fuel

TVERLANDET VEISERVICE AS

Org. no. 920492193 Limited company (AS) Bodø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 10.6m
Operating profit NOK 162,000
Equity NOK 285,000
Incorporated 2018
Employees 14
Share capital NOK 30,000

TVERLANDET VEISERVICE AS is registered as a limited company in Bodø, Nordland with organisation number 920492193. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2018 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive bensinstasjon og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.6m in revenue and NOK 162,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.6m
Operating profit
NOK 162,000
Equity
NOK 285,000
Est. value
NOK 774,000

Financial health · 2024

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

Who owns TVERLANDET VEISERVICE AS?

OMALO HOLDING AS
TVERLANDET VEISERVICE AS
NOK 10.6m rev. · NOK 162,000 profit

TVERLANDET VEISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TVERLANDET VEISERVICE AS

Who owns TVERLANDET VEISERVICE AS?

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

What is the revenue of TVERLANDET VEISERVICE AS?

TVERLANDET VEISERVICE AS had revenue of NOK 10.6m in 2024.

Who is the general manager of TVERLANDET VEISERVICE AS?

Ole Marius Løberg is registered as general manager of TVERLANDET VEISERVICE AS.

Where is TVERLANDET VEISERVICE AS based?

TVERLANDET VEISERVICE AS has its business address in Tverlandet.

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.