biztrac. BETA
COMPANY REGISTER PROFILE
936372716 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

FILMON ABRAHAM AS

Org. no. 936372716 Limited company (AS) Hå Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

FILMON ABRAHAM AS is registered as a limited company in Hå, Rogaland with organisation number 936372716. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen eiendomssalg - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns FILMON ABRAHAM AS?

FILMON ABRAHAM AS
NOK 0 rev. · NOK 0 profit

FILMON ABRAHAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FILMON ABRAHAM AS

Who owns FILMON ABRAHAM AS?

Filmon Abraham is the largest registered owner, with 100.0%.

What is the revenue of FILMON ABRAHAM AS?

FILMON ABRAHAM AS had revenue of NOK 0 in 2025.

Who is the general manager of FILMON ABRAHAM AS?

Filmon Abraham is registered as general manager of FILMON ABRAHAM AS.

Where is FILMON ABRAHAM AS based?

FILMON ABRAHAM AS has its business address in Nærbø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.