BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

PÅ POSTEN AS

Org. no. 918546839 Limited company (AS) Hvaler Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 19,000
Equity NOK −2.5m
Incorporated 2017
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,5 mill kr).

PÅ POSTEN AS is registered as a limited company in Hvaler, Østfold with organisation number 918546839. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Detaljhandel med interiør og utstyr, samt cafe drift.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 19,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 19,000
Equity
NOK −2.5m
Est. value
NOK 98,000

Financial health · 2024

Liquidity
4.41
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-152.2%
Weak
Equity as a share of total capital

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

Who owns PÅ POSTEN AS?

LARS PETTER BUSTGAARD
PÅ POSTEN AS
NOK 2.5m rev. · NOK 19,000 profit

PÅ POSTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PÅ POSTEN AS

Who owns PÅ POSTEN AS?

LARS PETTER BUSTGAARD is the largest registered owner, with 50.0%.

What is the revenue of PÅ POSTEN AS?

PÅ POSTEN AS had revenue of NOK 2.5m in 2024.

Who is the general manager of PÅ POSTEN AS?

Gry-Hege Bustgaard is registered as general manager of PÅ POSTEN AS.

Where is PÅ POSTEN AS based?

PÅ POSTEN AS has its business address in Herføl.

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.