BIZTRAC BETA
Intermediation service activities for real estate activities

INFINITA EIENDOMSMEGLING AS

Org. no. 913151879 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 15.2m
Operating profit NOK 1.4m
Equity NOK 1.2m
Incorporated 2014
Employees 9
Share capital NOK 100,000

INFINITA EIENDOMSMEGLING AS is registered as a limited company in Oslo, Oslo with organisation number 913151879. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive eiendomsmegling.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.2m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 15.2m
Operating profit
NOK 1.4m
Equity
NOK 1.2m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns INFINITA EIENDOMSMEGLING AS?

JEG HOLDING AS
INFINITA EIENDOMSMEGLING AS
NOK 15.2m rev. · NOK 1.4m profit

INFINITA EIENDOMSMEGLING AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about INFINITA EIENDOMSMEGLING AS

Who owns INFINITA EIENDOMSMEGLING AS?

JEG HOLDING AS is the largest registered owner, with 35.9%.

What is the revenue of INFINITA EIENDOMSMEGLING AS?

INFINITA EIENDOMSMEGLING AS had revenue of NOK 15.2m in 2024.

Who is the general manager of INFINITA EIENDOMSMEGLING AS?

Bent Walther Johansen is registered as general manager of INFINITA EIENDOMSMEGLING AS.

Where is INFINITA EIENDOMSMEGLING AS based?

INFINITA EIENDOMSMEGLING AS has its business address in Oslo.

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.