BIZTRAC BETA
Retail sale of automotive fuel

TIDEMANN BIL AS

Org. no. 984406622 Limited company (AS) Meløy Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 20.2m
Operating profit NOK 63,000
Equity NOK 236,000
Incorporated 2002
Employees 6
Share capital NOK 200,000

TIDEMANN BIL AS is registered as a limited company in Meløy, Nordland with organisation number 984406622. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2002 and has 6 registered employees. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Å drive bensinstasjon og hva dermed står i forbindelse, herunder å delta i andre selskaper med lignenede virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.2m in revenue and NOK 63,000 in operating profit.

Key figures · 2024

Revenue
NOK 20.2m
Operating profit
NOK 63,000
Equity
NOK 236,000
Est. value
NOK 295,000

Financial health · 2024

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.9%
Weak
Equity as a share of total capital

Who owns TIDEMANN BIL AS?

ULF-EIRIK TIDEMANN
TIDEMANN BIL AS
NOK 20.2m rev. · NOK 63,000 profit

TIDEMANN BIL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIDEMANN BIL AS own?

TIDEMANN BIL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TIDEMANN BIL AS

Who owns TIDEMANN BIL AS?

ULF-EIRIK TIDEMANN is the largest registered owner, with 100.0%.

What is the revenue of TIDEMANN BIL AS?

TIDEMANN BIL AS had revenue of NOK 20.2m in 2024.

Who is the general manager of TIDEMANN BIL AS?

Ulf-Eirik Tidemann is registered as general manager of TIDEMANN BIL AS.

Where is TIDEMANN BIL AS based?

TIDEMANN BIL AS has its business address in Ørnes.

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.