BIZTRAC BETA
Rental and operating of own or leased real estate

E BRIX AS

Org. no. 880981242 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −1.8m
Equity NOK 47.2m
Incorporated 1999
Share capital NOK 339,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,8 mill kr).

E BRIX AS is registered as a limited company in Oslo, Oslo with organisation number 880981242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 339,000, divided into 3386 shares. The company's stated purpose is: “Investere i selskaper, eiendom og aksjer. Å aktivt være med på å videreutvikle de selskaper som man velger å engasjere seg i.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −1.8m in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −1.8m
Equity
NOK 47.2m
Est. value
NOK 33.7m

Financial health · 2024

Liquidity
15.42
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
95.0%
Very good
Equity as a share of total capital

Who owns E BRIX AS?

EDWARD MARTIN TAN
E BRIX AS
NOK 1.0m rev. · NOK −1.8m profit

E BRIX AS has 1 registered shareholder:

All shareholders and roles →

Which companies does E BRIX AS own?

E BRIX AS holds stakes in 18 companies:

See the full ownership structure →

Frequently asked questions about E BRIX AS

Who owns E BRIX AS?

EDWARD MARTIN TAN is the largest registered owner, with 100.0%.

What is the revenue of E BRIX AS?

E BRIX AS had revenue of NOK 1.0m in 2024.

Who is the general manager of E BRIX AS?

Edward Martin Tan is registered as general manager of E BRIX AS.

Where is E BRIX AS based?

E BRIX 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.