BIZTRAC BETA
Activities of advertising agencies

PUBLY AS

Org. no. 992585641 Limited company (AS) Frosta Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 374,000
Equity NOK −999,000
Incorporated 2008
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−999k kr).

PUBLY AS is registered as a limited company in Frosta, Trøndelag with organisation number 992585641. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2008. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Å tilby annonseløsninger på digitale flater samt utvikle programvare for distribusjon av innhold på skjerm og det som naturlig står i forbindelse med dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 374,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 374,000
Equity
NOK −999,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.55
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-165.0%
Weak
Equity as a share of total capital

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

Who owns PUBLY AS?

ULV HOLDING AS
PUBLY AS
NOK 1.3m rev. · NOK 374,000 profit

PUBLY AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PUBLY AS own?

PUBLY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PUBLY AS

Who owns PUBLY AS?

ULV HOLDING AS is the largest registered owner, with 54.0%.

What is the revenue of PUBLY AS?

PUBLY AS had revenue of NOK 1.3m in 2024.

Where is PUBLY AS based?

PUBLY AS has its business address in Frosta.

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.