BIZTRAC BETA
Construction of residential and non-residential buildings

H.THANKE BYGG AS

Org. no. 992831286 Limited company (AS) Ullensaker Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 181,000
Equity NOK 38,000
Incorporated 2008
Share capital NOK 100,000

H.THANKE BYGG AS is registered as a limited company in Ullensaker, Akershus with organisation number 992831286. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Renovering av bygninger og oppføring av nybygg, samt annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 181,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 181,000
Equity
NOK 38,000
Est. value
NOK 519,000

Financial health · 2024

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

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

Who owns H.THANKE BYGG AS?

HARRY THANKE
H.THANKE BYGG AS
NOK 1.3m rev. · NOK 181,000 profit

H.THANKE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about H.THANKE BYGG AS

Who owns H.THANKE BYGG AS?

HARRY THANKE is the largest registered owner, with 100.0%.

What is the revenue of H.THANKE BYGG AS?

H.THANKE BYGG AS had revenue of NOK 1.3m in 2024.

Who is the general manager of H.THANKE BYGG AS?

Harry Thanke is registered as general manager of H.THANKE BYGG AS.

Where is H.THANKE BYGG AS based?

H.THANKE BYGG AS has its business address in Jessheim.

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.