BIZTRAC BETA
Rental and operating of own or leased real estate

KRAMEK EIENDOM AS

Org. no. 989126180 Limited company (AS) Horten Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 579,000
Operating profit NOK 225,000
Equity NOK 931,000
Incorporated 2005
Share capital NOK 100,000

KRAMEK EIENDOM AS is registered as a limited company in Horten, Vestfold with organisation number 989126180. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Å drive utleie av fast eiendom og deltagelse i annen næringsvirksomhet forøvrig.”. The most recent filed accounts, for the 2024 financial year, show NOK 579,000 in revenue and NOK 225,000 in operating profit.

Key figures · 2024

Revenue
NOK 579,000
Operating profit
NOK 225,000
Equity
NOK 931,000
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns KRAMEK EIENDOM AS?

TERJE KRATHE
KRAMEK EIENDOM AS
NOK 579,000 rev. · NOK 225,000 profit

KRAMEK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRAMEK EIENDOM AS own?

KRAMEK EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KRAMEK EIENDOM AS

Who owns KRAMEK EIENDOM AS?

TERJE KRATHE is the largest registered owner, with 100.0%.

What is the revenue of KRAMEK EIENDOM AS?

KRAMEK EIENDOM AS had revenue of NOK 579,000 in 2024.

Who is the general manager of KRAMEK EIENDOM AS?

Terje Krathe is registered as general manager of KRAMEK EIENDOM AS.

Where is KRAMEK EIENDOM AS based?

KRAMEK EIENDOM AS has its business address in Horten.

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.