BIZTRAC BETA
Development of building projects

BEIT EMA AS

Org. no. 912781194 Limited company (AS) Flekkefjord Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −30,000
Equity NOK −600,000
Incorporated 2013
Share capital NOK 270,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−600k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−30k kr).

BEIT EMA AS is registered as a limited company in Flekkefjord, Agder with organisation number 912781194. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 270,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, eiendomsutvikling og annet som måtte komme inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK −600,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BEIT EMA AS?

Ellen Marie Helvig Skåland
BEIT EMA AS
NOK 0 rev. · NOK −30,000 profit

BEIT EMA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEIT EMA AS own?

BEIT EMA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BEIT EMA AS

Who owns BEIT EMA AS?

Ellen Marie Helvig Skåland is the largest registered owner, with 100.0%.

What is the revenue of BEIT EMA AS?

BEIT EMA AS had revenue of NOK 0 in 2025.

Where is BEIT EMA AS based?

BEIT EMA AS has its business address in Flekkefjord.

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.