BIZTRAC BETA
Publishing of newspapers

KLÆBUPOSTEN AS

Org. no. 890958532 Limited company (AS) Trondheim Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −2.2m
Equity NOK 600,000
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KLÆBUPOSTEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 890958532. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive med lokalavis, samt kunne delta i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −2.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −2.2m
Equity
NOK 600,000
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns KLÆBUPOSTEN AS?

POLARIS MEDIA MIDT-NORGE AS
KLÆBUPOSTEN AS
NOK 2.0m rev. · NOK −2.2m profit

KLÆBUPOSTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLÆBUPOSTEN AS

Who owns KLÆBUPOSTEN AS?

POLARIS MEDIA MIDT-NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of KLÆBUPOSTEN AS?

KLÆBUPOSTEN AS had revenue of NOK 2.0m in 2024.

Who is the general manager of KLÆBUPOSTEN AS?

Odd Arild Sandnes is registered as general manager of KLÆBUPOSTEN AS.

Where is KLÆBUPOSTEN AS based?

KLÆBUPOSTEN AS has its business address in Klæbu.

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.