BIZTRAC BETA
Rental and operating of own or leased real estate

BATEMAN NORDISK EIENDOM AS

Org. no. 922570078 Limited company (AS) Bardu Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.0m
Equity NOK 3.1m
Incorporated 2019
Share capital NOK 1.0m

BATEMAN NORDISK EIENDOM AS is registered as a limited company in Bardu, Troms with organisation number 922570078. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling, utleie og salg av fast eiendom. Selskapet kan delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.0m
Equity
NOK 3.1m
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.1%
Good
Equity as a share of total capital

Who owns BATEMAN NORDISK EIENDOM AS?

ROGER BRIAN BATEMAN
BATEMAN NORDISK EIENDOM AS
NOK 1.7m rev. · NOK 1.0m profit

BATEMAN NORDISK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BATEMAN NORDISK EIENDOM AS

Who owns BATEMAN NORDISK EIENDOM AS?

ROGER BRIAN BATEMAN is the largest registered owner, with 100.0%.

What is the revenue of BATEMAN NORDISK EIENDOM AS?

BATEMAN NORDISK EIENDOM AS had revenue of NOK 1.7m in 2024.

Who is the general manager of BATEMAN NORDISK EIENDOM AS?

Roger Brian Bateman is registered as general manager of BATEMAN NORDISK EIENDOM AS.

Where is BATEMAN NORDISK EIENDOM AS based?

BATEMAN NORDISK EIENDOM AS has its business address in Bardu.

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.