BIZTRAC BETA
Construction of residential and non-residential buildings

KERAMA BYGG AS

Org. no. 934097610 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 432,000
Operating profit NOK −159,000
Equity NOK −107,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

KERAMA BYGG AS is registered as a limited company in Lillestrøm, Akershus with organisation number 934097610. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Oppføring av bygninger. Byggearbeider, byggeservice, samt annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 432,000 in revenue and NOK −159,000 in operating profit.

Key figures · 2025

Revenue
NOK 432,000
Operating profit
NOK −159,000
Equity
NOK −107,000

Financial health · 2025

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

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

Who owns KERAMA BYGG AS?

Genadij Panasevic
KERAMA BYGG AS
NOK 432,000 rev. · NOK −159,000 profit

KERAMA BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KERAMA BYGG AS

Who owns KERAMA BYGG AS?

Genadij Panasevic is the largest registered owner, with 100.0%.

What is the revenue of KERAMA BYGG AS?

KERAMA BYGG AS had revenue of NOK 432,000 in 2025.

Where is KERAMA BYGG AS based?

KERAMA BYGG AS has its business address in Frogner.

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.