BIZTRAC BETA
Plumbing installation

T&K GRANLUND HOLDING AS

Org. no. 931408070 Limited company (AS) Rælingen Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 11,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

T&K GRANLUND HOLDING AS is registered as a limited company in Rælingen, Akershus with organisation number 931408070. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen investering i aksjer, verdipapirer og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK 11,000
Est. value
NOK 11,000

Financial health · 2025

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

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

Who owns T&K GRANLUND HOLDING AS?

KEN GRANLUND
T&K GRANLUND HOLDING AS
· NOK −11,000 profit

T&K GRANLUND HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does T&K GRANLUND HOLDING AS own?

T&K GRANLUND HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about T&K GRANLUND HOLDING AS

Who owns T&K GRANLUND HOLDING AS?

KEN GRANLUND is the largest registered owner, with 50.0%.

Who is the general manager of T&K GRANLUND HOLDING AS?

Ken Granlund is registered as general manager of T&K GRANLUND HOLDING AS.

Where is T&K GRANLUND HOLDING AS based?

T&K GRANLUND HOLDING AS has its business address in Fjerdingby.

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.