BIZTRAC BETA
Arts creation activities in literature

POLLINATION PUBLISHING AS

Org. no. 914850053 Limited company (AS) Eidsvoll Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 306,000
Equity NOK 332,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-19 Adresseendring registrert 2026-02-19.

POLLINATION PUBLISHING AS is registered as a limited company in Eidsvoll, Akershus with organisation number 914850053. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Journalistisk virksomhet innen IT og data .”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 306,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 306,000
Equity
NOK 332,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns POLLINATION PUBLISHING AS?

TROND BJARNE BIE
POLLINATION PUBLISHING AS
NOK 2.8m rev. · NOK 306,000 profit

POLLINATION PUBLISHING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about POLLINATION PUBLISHING AS

Who owns POLLINATION PUBLISHING AS?

TROND BJARNE BIE is the largest registered owner, with 66.7%.

What is the revenue of POLLINATION PUBLISHING AS?

POLLINATION PUBLISHING AS had revenue of NOK 2.8m in 2024.

Who is the general manager of POLLINATION PUBLISHING AS?

Trond Bjarne Bie is registered as general manager of POLLINATION PUBLISHING AS.

Where is POLLINATION PUBLISHING AS based?

POLLINATION PUBLISHING AS has its business address in Eidsvoll.

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.